found 645636 git/1:1.7.7-2
notfound 645636 git/1:1.7.2.5-3
retitle 645636 "git branch -M" refuses to clobber current branch
quit
Soeren Sonnenburg wrote:
> Well that works in git 1.7.2.X up to version 1.7.6-X but no longer in at
> least 1.7.7-2
Ah, why didn't you say that in the first place? :) Please make sure
to set the 'Version:' pseudo-header correctly in cases like this in
the future.
This was a deliberate change: see v1.7.7-rc2~1^2~2 (Prevent
force-updating of the current branch, 2011-08-20). If I run
git checkout -b master origin/topic1
git branch topic origin/topic2
git branch -M topic master
then what should happen to my working tree? It is a very strange
operation.
I do believe it would be intuitive to make "checkout -B" (but not
"branch -M") handle this case specially and might propose a patch to
do that if a spare moment comes.
Anyway, your best bet in getting your preferred behavior implemented
is to talk to upstream ([email protected]), preferrably with a
proof-of-concept patch illustrating what that behavior is. They're
generally a friendly bunch; no subscription required, and the
convention is to always reply-to-all there.
Sorry for the trouble, and hope that clarifies a little.
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
