From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-branch -m cannot rename remote branches
Date: Mon, 9 Jun 2008 09:06:50 +0200 [thread overview]
Message-ID: <200806090906.51937.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0806082357470.1783@racer>
On Mon, 9 Jun 2008, Johannes Schindelin wrote:
> On Sun, 8 Jun 2008, Jakub Narebski wrote:
>
> > I cannot rename remote branch (possibly packed, and possibly with
> > reflog) using "git branch"
>
> 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.
What I really wanted was "git remote rename <old-name> <new-name>",
together with renaming branches and moving reflogs. I can do first
part by editing config file ("git remote rename"/"git remote mv"
probably would want to assume that user wants to move branches if
they follow remotes/<old-name>/* calling convention; ask user if it
is not the case?). I thought that I could use "git branch -m" for
the other... I was left with editing packed-refs file (BTW. is leaving
empty directory 'xx' when packing 'xx/name' branch by design?) and
moving reflog by hand.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-06-09 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 20:57 [BUG] git-branch -m cannot rename remote branches Jakub Narebski
2008-06-08 22:58 ` Johannes Schindelin
2008-06-09 7:06 ` Jakub Narebski [this message]
2008-06-09 12:53 ` Olivier Marin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806090906.51937.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).