From: John Wiegley <jwiegley@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Robert Weiner <rswgnu@gmail.com>,
emacs-devel <emacs-devel@gnu.org>,
Sven Axelsson <sven.axelsson@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: Re: git replace --edit for updating commit messages
Date: Tue, 02 Aug 2016 16:37:47 -0700 [thread overview]
Message-ID: <m2vazilp2s.fsf@newartisans.com> (raw)
In-Reply-To: <mvmpopy18z2.fsf@hawking.suse.de> (Andreas Schwab's message of "Thu, 28 Jul 2016 10:07:45 +0200")
>>>>> "AS" == Andreas Schwab <schwab@suse.de> writes:
AS> FWIW, there is ongoing work to add a refs API that allows plugging in a
AS> different backend to store references, to scale better with the number of
AS> refs.
Also, wouldn't it be possible to exclude these refs from being pulled, so that
only those who actually need to see the updated commit messages pay any cost?
If the cost is neglible for a small number of revised commits (for now), it
doesn't seem too scary.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-08-02 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 1:35 git replace --edit for updating commit messages (was: Is it time to drop ChangeLogs?) Noam Postavsky
2016-07-28 8:07 ` git replace --edit for updating commit messages Andreas Schwab
2016-08-02 23:37 ` John Wiegley [this message]
2016-08-03 6:49 ` Andreas Schwab
2016-07-28 14:43 ` git replace --edit for updating commit messages (was: Is it time to drop ChangeLogs?) Eli Zaretskii
2016-07-30 23:18 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vazilp2s.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
--cc=rswgnu@gmail.com \
--cc=schwab@suse.de \
--cc=sven.axelsson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).