Re: [BUG] git-branch -m cannot rename remote branches

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Johannes Schindelin
Date: Sunday, June 8, 2008 - 3:58 pm

Hi,

On Sun, 8 Jun 2008, Jakub Narebski wrote:


That is very much by design; a next fetch would get them with their 
current name anyway.  A "remote prune" should get rid of any stale 
branches.

So yes, "branch -m" with remote branches does not make sense.

Ciao,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[BUG] git-branch -m cannot rename remote branches, Jakub Narebski, (Sun Jun 8, 1:57 pm)
Re: [BUG] git-branch -m cannot rename remote branches, Johannes Schindelin, (Sun Jun 8, 3:58 pm)
Re: [BUG] git-branch -m cannot rename remote branches, Jakub Narebski, (Mon Jun 9, 12:06 am)
Re: [BUG] git-branch -m cannot rename remote branches, Olivier Marin, (Mon Jun 9, 5:53 am)