From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: Wrong commit message. What to do now?
Date: Wed, 14 Jul 2010 02:54:40 +0200 [thread overview]
Message-ID: <877hkydgrz.fsf@telefonica.net> (raw)
In-Reply-To: <871vb6dhm7.fsf@red-bean.com> (Karl Fogel's message of "Tue, 13 Jul 2010 20:36:32 -0400")
CC'ing emacs-devel
Karl Fogel <kfogel@red-bean.com> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>>Stefan asked for it on the bzr mailing list:
>>http://article.gmane.org/gmane.comp.version-control.bazaar-ng.general/39686
>>(click on the Subject for seeing all the thread)
>>IIRC it was filed in the "wishlist" category, "pie in the sky" priority :-)
>
> The two most recent revisions are still mine (the second-to-last one
> has the botched commit message). I could 'bzr uncommit' them, fix, and
> recommit in order.
>
> But how would this play with everyone else who may have pulled changes
> from the trunk into their local branches already?
You would create some irritating problems for those. They need to notice
the problem (usually the next time the pull), figure out what is it, and
solve it. Possibly with bzr revert, or deleting `trunk' and cloning
again from upstream. Maybe the shared repository will save downloading
almost all of the revisions.
> That means I effectively can't uncommit, right?
You can't uncommit. The bzr repo at Savannah has a rule that forbids
that.
next prev parent reply other threads:[~2010-07-14 0:54 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 [this message]
2010-07-26 22:49 ` Stefan Monnier
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=877hkydgrz.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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 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.