{"thread":{"id":"29958","subject":"[BUG?] git branch -m doesn't update tracked branch config","startedAt":"2012-03-15T15:51:05Z","lastAt":"2012-03-15T20:52:43Z","messageCount":2,"participants":["Dave Borowitz","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"187047","messageId":"CAD0k6qRWR9H8BejcXx3gzy2yQT_MjRBDtbZzhLVM215HQiaVhg@mail.gmail.com","threadId":"29958","inReplyTo":null,"subject":"[BUG?] git branch -m doesn't update tracked branch config","fromName":"Dave Borowitz","fromEmail":"dborowitz@google.com","sentAt":"2012-03-15T15:51:05Z","receivedAt":"2012-03-15T15:51:05Z","isPatch":false,"sender":{"key":"dborowitz@google.com","avatar":"https://avatars.githubusercontent.com/u/194927?v=4"},"body":"$ git branch --track branch master\nBranch branch set up to track local branch master.\n$ git branch -m master newmaster\n$ git branch -vv\n  branch    e8fadc2 [master] foo\n* newmaster e8fadc2 foo\n\nI would have expected branch's upstream to now be newmaster rather\nthan master, or at the very least some warning that branch now has a\nnonexistent upstream. Is this intended behavior, or a bug?\n"},{"id":"187056","messageId":"7v7gylk2n8.fsf@alter.siamese.dyndns.org","threadId":"29958","inReplyTo":"CAD0k6qRWR9H8BejcXx3gzy2yQT_MjRBDtbZzhLVM215HQiaVhg@mail.gmail.com","subject":"Re: [BUG?] git branch -m doesn't update tracked branch config","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-15T20:52:43Z","receivedAt":"2012-03-15T20:52:43Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Dave Borowitz <dborowitz@google.com> writes:\n\n> $ git branch --track branch master\n> Branch branch set up to track local branch master.\n> $ git branch -m master newmaster\n> $ git branch -vv\n>   branch    e8fadc2 [master] foo\n> * newmaster e8fadc2 foo\n>\n> I would have expected branch's upstream to now be newmaster rather\n> than master, or at the very least some warning that branch now has a\n> nonexistent upstream. Is this intended behavior, or a bug?\n\nI think \"branch -m A B\" moves everything in \"branch.A.*\" over to\n\"branch.B.*\" and does nothing else.\n\nYou would also want to find all Cs that have \"branch.C.merge = A\"\nand \"branch.C.remote = .\" and update A in them to B, or something.\n"}]}