[ I get really really annoyed when your replies to me aren't directly
addressed to me, Jakub. Told you so repeatedly in the past as well.
Why are you the only one on this list apparently not able to use a
proper email setup? ]
On Mon, 26 Nov 2007, Jakub Narebski wrote:
> Nicolas Pitre wrote:
>
> > Some stuff gets rebased because it has to be refined before it is
> > merged in a more stable and more "official" repository. Working on
> > top of a rebased branch could be much easier if there was a
> > dedicated command to perform the local rebase of one's work after a
> > fetch, just like the pull command does a merge after a fetch, at
> > which point both work flows would be almost equivalent wrt ease of
> > use.
>
> There was idea of 'rebase' merge strategy (which was in some form
> implemented once under another name: check archives if you want).
> And there is an idea of --rebase switch git git-pull.
>
> What is left is the implementation ;-)
I thought that had been implemented already. But in fact I had forgot
about it altogether.
It shouldn't be much complicated than:
git fetch ${remote} && \
git rebase --onto ${remote} ${remote}"@{1}" ${local}
given that ${remote} did actually change during the fetch.
Nicolas
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
