On Fri, May 23, 2014 at 10:10:05AM -0700, Junio C Hamano wrote:
> John Keeping <j...@keeping.me.uk> writes:
> > On Fri, May 23, 2014 at 02:11:55PM +0400, Sergei Organov wrote:
> >> Hello,
> >> After convertion of a project from CVS to git, I'd like to rename some
> >> references in the created git repository (before it's published, so no
> >> problems here). Is there a plumbing that would do:
> >> git rename-ref <old_name> <new_name>
> >> for me?
> > I think the best you can get is two invocations of `git update-ref`:
> > git update-ref <new_name> <old_name> &&
> > git update-ref -d <old_name>
> > Although if you're scripting it the `--stdin` mode may be easier:
> > git update-ref --stdin <<-\EOF
> > create <new_name> <old_name>
> > delete <old_name>
> > EOF
> > Note that "<new_name>" must be a fully-qualified ref (that is, it must
> > start with "refs/", so "refs/heads/new_name" for a branch or
> > "refs/tags/new_name" for a tag).
> Shouldn't <old_name> also be a full ref?
I tested this before sending the email, and it seemed to do the right
thing specifying only the branch name; so it probably /should/ be a full
ref, but it seems like it doesn't /need/ to be.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html