From: Miles Bader <miles.bader@necel.com>
To: git@vger.kernel.org
Subject: renaming remote branches
Date: Thu, 16 Apr 2009 12:27:31 +0900 [thread overview]
Message-ID: <buo3ac9jn18.fsf@dhlpc061.dev.necel.com> (raw)
I can "rename" a remote branch by doing:
git push REMOTE REMOTE/OLD:refs/heads/NEW
git push REMOTE :OLD
is there any better way to do this (I mean, er... more
user-friendly/less-dangerous/... I dunno... "better" :-)?
Also, I note that the old name ("OLD") remains in .git/info/refs, both
locally and in the remote; is this a problem? I can update the local
.git/info/refs by running "git update-server-info", but I'm not sure how
to do in for the remote repo without having a login there...
Thanks,
-miles
--
Erudition, n. Dust shaken out of a book into an empty skull.
next reply other threads:[~2009-04-16 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 3:27 Miles Bader [this message]
2009-04-16 6:59 ` renaming remote branches Jeff King
2009-04-16 8:00 ` Miles Bader
2009-04-16 8:18 ` Jeff King
2009-04-16 13:09 ` Jay Soffian
2009-04-16 13:50 ` Jeff King
2009-04-17 0:51 ` Miles Bader
2009-04-17 12:07 ` Jeff King
2009-04-17 16:20 ` Dmitry Potapov
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=buo3ac9jn18.fsf@dhlpc061.dev.necel.com \
--to=miles.bader@necel.com \
--cc=git@vger.kernel.org \
--cc=miles@gnu.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).