From: Junio C Hamano <gitster@pobox.com>
To: Deskin Miller <deskinm@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, Jay Soffian <jaysoffian@gmail.com>
Subject: Re: [PATCH v2 2/2] Teach @{-1} to git merge
Date: Thu, 26 Feb 2009 21:24:21 -0800 [thread overview]
Message-ID: <7veixkpi4a.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <86d4c5e00902262027y13b19eb7nf89a45e83b986801@mail.gmail.com> (Deskin Miller's message of "Thu, 26 Feb 2009 23:27:05 -0500")
Deskin Miller <deskinm@gmail.com> writes:
> I did 'git branch -M @{-1}' yesterday and ended up renaming my branch
> to refs/heads/@{-1}. Personally my usage felt like it should work
> (but of course I think that); curious to know what others think, if
> this is a bug.
The @{-n} notation is supposed to be usable anywhere you would write a
branch name and should behave as if you wrote the name itself. And 'git
branch -M <name> [<name>]' does expect a branch name, not a random
extended SHA-1 expression.
I'd say it is a bug.
next prev parent reply other threads:[~2009-02-27 5:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 7:08 [PATCH] teach the new "@{-1} syntax to "git branch" Junio C Hamano
2009-02-14 7:11 ` Jay Soffian
2009-02-14 7:21 ` Junio C Hamano
2009-02-14 9:37 ` [PATCH v2 1/2] Teach the " Junio C Hamano
2009-02-14 9:39 ` [PATCH v2 2/2] Teach @{-1} to git merge Junio C Hamano
2009-02-14 22:52 ` Johannes Schindelin
2009-02-15 2:05 ` Junio C Hamano
2009-02-15 2:32 ` Junio C Hamano
2009-02-15 9:24 ` Nanako Shiraishi
2009-02-15 10:02 ` Junio C Hamano
2009-02-15 11:21 ` Johannes Schindelin
2009-02-16 4:16 ` Junio C Hamano
2009-02-16 10:41 ` Johannes Schindelin
2009-02-16 16:40 ` Jay Soffian
2009-02-26 0:11 ` Junio C Hamano
2009-02-26 10:18 ` Johannes Schindelin
2009-02-27 4:27 ` Deskin Miller
2009-02-27 5:24 ` Junio C Hamano [this message]
2009-02-27 6:10 ` [PATCH] git-branch: a detached HEAD and branch called HEAD are different Junio C Hamano
2009-02-27 6:12 ` [PATCH] "git branch -M @{-1}" Junio C Hamano
2009-02-27 6:49 ` Junio C Hamano
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=7veixkpi4a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=deskinm@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.