Fix committer name ?
Michael Gliwinski
Michael.Gliwinski at henderson-group.com
Wed Jul 22 12:23:01 BST 2009
Xavier Maillard <xma <at> gnu.org> writes:
>
> At Tue, 26 May 2009 15:08:29 +0900,
> Stephen J. Turnbull wrote:
> >
> > Andrew Cowie writes:
> >
> > > On Mon, 2009-05-25 at 12:48 +0200, Xavier MAILLARD wrote:
> > > > I need to read about rebase.
> > >
> > > [as I understand it:]
> > >
> > > Rebasing creates new [completely new] revisions with content similar to
> > > the set it is replacing.
> >
> > This is correct, except that the content is *identical*. So if Xavier
> > merges his rebased branch with the old head *immediately*, he should
> > get zero conflicts. I wonder if this might not be a solution for
> > Xavier:
> >
> > 1. create a copy branch
> > 2. rebase the original
> > 3. merge *from* the copy into the (rebased) original
> > 4. have downstream merge as usual
>
> Maybe I am too stupid but I tried that:
>
> 1. bzr branch (to get a copy)
> 2. bzr rebase
> => No revisions to rebase
>
> I am not sure I understand all of this after all.
>
> Plus, bzr-rebase is not very clear (no examples) of what and how
> things should be done.
>
> Xavier
>
>
I have the same problem with two of my projects. Was wondering have you ever
figured out how to fix that (with rebase or otherwise)?
I've had a look at rebase but I must admit I also don't see how it should
allow you to change the committer/author. Also I have the bad committer name
only on some of the revisions as I work on the code from different locations
(in different branches) and merge from time to time (i.e. whoami was wrong
only in one of those locations).
Any advice?
Thanks,
Michael
More information about the bazaar
mailing list