From: Paul Eggert <eggert@cs.ucla.edu>
To: Robin Templeton <robin@terpri.org>, emacs-devel@gnu.org
Subject: Re: master cbef1e9 2/3: ; make change-history-commit
Date: Thu, 09 Apr 2015 22:41:02 -0700 [thread overview]
Message-ID: <5527626E.7040307@cs.ucla.edu> (raw)
In-Reply-To: <87y4m1rkuq.fsf@panthera.terpri.org>
Robin Templeton wrote:
> If only corrections to specific commits were stored,
> it would be possible to amend the log messages as viewed with git
> commands, perhaps using git object notes.
I originally proposed that -- it's the approach Coreutils takes -- but the
Coreutils approach turns out to be too much of a pain to understand and use in
the context of Emacs development. Glenn did suggest object notes, but as I
understand it Emacs VC doesn't support them. So I went with the best
easy-enough approach that I could think of, an approach based on Emacs's
tradition of ChangeLog history files. If we can think of something better, we
should switch to it.
> Separating corrections could also completely eliminate ChangeLog merge
> conflicts.
I don't see how. No matter how one versions corrections, merge conflicts can
occur if concurrent developers generate different corrections for the same
ChangeLog entry. Perhaps Git wouldn't identify them as conflicts, but they'd
still be conflicts. Certainly object notes can have conflicts.
That being said, I expect the current scheme will greatly reduce merge conflicts
in practice. For example, I expect it would have avoided RMS's merge conflict
that started that looooong recent thread.
next prev parent reply other threads:[~2015-04-10 5:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150409172246.20602.44549@vcs.savannah.gnu.org>
[not found] ` <E1YgGAB-0005NP-Uc@vcs.savannah.gnu.org>
2015-04-09 18:24 ` master cbef1e9 2/3: ; make change-history-commit Glenn Morris
2015-04-09 20:26 ` Paul Eggert
2015-04-13 2:19 ` Glenn Morris
2015-04-13 6:58 ` Paul Eggert
2015-04-15 17:32 ` Glenn Morris
2015-04-15 17:39 ` Glenn Morris
2015-04-15 21:30 ` Paul Eggert
2015-04-09 22:35 ` Robin Templeton
2015-04-10 5:41 ` Paul Eggert [this message]
2015-04-11 4:33 ` Dmitry Gutov
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=5527626E.7040307@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=robin@terpri.org \
/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).