Changeset identity

Lukáš Lalinský lalinsky at
Wed Jul 30 10:25:36 BST 2008

Dňa St, 2008-07-30 o 10:20 +0100, James Westby napísal:
> > The issue
> > then is that the changeset already has a commit message and no new
> > commit message is needed so any sequence that requires an explicit
> > commit seems sub-optimal, indeed unnecessary.
> You could write a command that did the same as "git cherry-pick",
> which did the cherry-pick merge, and then automatically commited
> with the same message, optionally adding a "cherry picked from
> bla bla bla" message. The commit is required, but it could be
> automated (assuming there are no conflicts).
> The only way I can think of to avoid the commit message is to use
> rebase. I think it would be more effort, and it could be argued that
> it just re-uses the commit message in the same way that I just
> described.

Such command already exists (except that you can't edit the commit
message like in `git cherry-pick --edit`), it's in the bzr-rebase
plugin, and it's called `bzr replay`.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Toto je =?ISO-8859-1?Q?digit=E1lne?=
	=?ISO-8859-1?Q?_podp=EDsan=E1?= =?UTF-8?Q?_=C4=8Das=C5=A5?=
Url : 

More information about the bazaar mailing list