Usability of git-update-ref <headname>

Usability of git-update-ref <headname>

[Martin Langhoff]

A few times now I've done the following

  # I think I'm on master, but I'm acually on maint
  git-branch foo-feature
  git-checkout foo-feature

  # realise I've branched in the wring place
  git-update-ref foo-feature master

And from that point, all sorts of things go weird, because I should have said

  git-update-ref refs/heads/foo-feature master

to fix it up I have to manually rm .git/foo-feature -- and I can't see
a way to remove a ref with git-update-ref, so if I was using packed
refs I'd be in trouble ;-)

Am I using the wrong command? I'd be happy to remove the bogus head
and create a new one, but I don't think we have git-rm-ref.



m

Re: Usability of git-update-ref <headname>

[Junio C Hamano]

"Martin Langhoff" <martin.langhoff@gmail.com> writes:

> Am I using the wrong command? I'd be happy to remove the bogus head
> and create a new one, but I don't think we have git-rm-ref.

Yes you are.  Forget about update-ref.  That is strictly for
script consumption.

>  # I think I'm on master, but I'm acually on maint
>  git-branch foo-feature
>  git-checkout foo-feature
>
>  # realise I've branched in the wrong place

   $ git reset --soft master