From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Jay Soffian <jaysoffian@gmail.com>
Subject: Re: [PATCH v2 2/2] Teach @{-1} to git merge
Date: Sun, 15 Feb 2009 20:16:47 -0800 [thread overview]
Message-ID: <7v1vtzf234.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0902151212320.10279@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Sun, 15 Feb 2009 12:21:44 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> In the name of consistency, I'd rather leave show-branch as it is.
Yes, Nana explained why I was wrong on this one.
> However, IMO there is a much worse issue lurking: people might want to
> _know_ what "@{-2}" would expand to, _without_ switching branches.
"git branch --history" anyone?
next prev parent reply other threads:[~2009-02-16 4:18 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 [this message]
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
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=7v1vtzf234.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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 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).