From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 15 Mar 2012 20:52:43 GMT
Subject: Re: [BUG?] git branch -m doesn't update tracked branch config
Message-ID: <7v7gylk2n8.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAD0k6qRWR9H8BejcXx3gzy2yQT_MjRBDtbZzhLVM215HQiaVhg@mail.gmail.com>

Dave Borowitz <dborowitz@google.com> writes:

> $ git branch --track branch master
> Branch branch set up to track local branch master.
> $ git branch -m master newmaster
> $ git branch -vv
>   branch    e8fadc2 [master] foo
> * newmaster e8fadc2 foo
>
> I would have expected branch's upstream to now be newmaster rather
> than master, or at the very least some warning that branch now has a
> nonexistent upstream. Is this intended behavior, or a bug?

I think "branch -m A B" moves everything in "branch.A.*" over to
"branch.B.*" and does nothing else.

You would also want to find all Cs that have "branch.C.merge = A"
and "branch.C.remote = ." and update A in them to B, or something.