Hi, On Thu, Dec 31, 2009 at 6:24 AM, Sylvain Rabot <sylvain@xxxxxxxxxxxxxx> wrote: > And then, at the end of the rebase, without me doing anything, feature > branch is checked out and it seems that its HEAD has been reset to the > new 12.72.1 HEAD. > > --x--x--x--x--x--x--x--x--x--x--x--x master > \ > o--o--o--o--o--o--o--a--a--a--a--a--a--a--a--a 12.72.1 feature > > Is that normal ? If it is, how do I do to avoid my feature branch to be > reset at 12.72.1's HEAD ? reading the manual, I think this is normal. According to the third paragraph of the description of git-rebase, the branch feature will be reset to 12.72.1. You can just rename the branch back to 12.72.1, and retrieve the old tip of feature by examining the reflog. -- Cheers, Ray Chuan -- 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