From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Karl Fogel <kfogel@red-bean.com>, emacs-devel@gnu.org
Subject: Re: Wrong commit message. What to do now?
Date: Tue, 27 Jul 2010 00:49:01 +0200 [thread overview]
Message-ID: <jwvlj8xn9rf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87hbk3c5ys.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Wed, 14 Jul 2010 01:33:31 +0200")
> git uses a different method, adding a concept of "annotations to a
> commit," which are not part of the commit's identity but are
> automatically displayed by tools like "git log". AIUI, this is
> backward compatible, but old git versions can't see the annotations.
> I suspect this would be fairly easy to implement in Bazaar, but I
> don't know anything about the relevant internals. I "like" this
> approach better, but can't prove it.
This is the way Bzr will solve the problem, tho only once heel freezes
over (as opposed to the other solutions which Bzr wouldn't use even if
hell freezes over).
The main reasons to way for that fateful event is that they can't decide
of a way to keep track of those annotations which would be Right (IIRC,
the issue is that OT1H it needs to use a special format which should be
upgradable, but OTOH it needs to be user-visible since there might be
conflicts between different annotations coming from different branches).
So rather than being pragmatic, they prefer to wait until the
parallels meet at which point those tensions will finally disappear.
Stefan
next prev parent reply other threads:[~2010-07-26 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 22:16 Wrong commit message. What to do now? Karl Fogel
2010-07-13 22:43 ` Óscar Fuentes
2010-07-13 23:17 ` Karl Fogel
2010-07-13 23:33 ` Óscar Fuentes
[not found] ` <871vb6dhm7.fsf@red-bean.com>
2010-07-14 0:54 ` Óscar Fuentes
2010-07-26 22:49 ` Stefan Monnier [this message]
2010-07-14 3:23 ` Stephen J. Turnbull
2010-07-14 3:42 ` Karl Fogel
2010-07-14 6:29 ` Eli Zaretskii
2010-07-14 15:29 ` Karl Fogel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvlj8xn9rf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=ofv@wanadoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.