Re: [PATCH v2 2/2] Teach @{-1} to git merge

3 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH v2 2/2] Teach @{-1} to git merge

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:46:12

Johannes Schindelin [off-list ref] 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?

Re: [PATCH v2 2/2] Teach @{-1} to git merge

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:46:12

Hi,

On Sun, 15 Feb 2009, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
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?
For a moment, you had me convinced it already exists, and I only 
understood after "git grep history builtin-branch.c" came up empty.

;-)

Ciao,
Dscho

Re: [PATCH v2 2/2] Teach @{-1} to git merge

From: Jay Soffian <hidden>
Date: 2016-06-15 22:46:12

On Mon, Feb 16, 2009 at 5:41 AM, Johannes Schindelin
[off-list ref] wrote:
quoted
"git branch --history" anyone?
For a moment, you had me convinced it already exists, and I only
understood after "git grep history builtin-branch.c" came up empty.
And I've labeled that mail as TODO. :-)

j.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help