Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: [PATCH 3/3] show-branch --reflog: show the reflog message at the top.

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:42:50

Hi,

On Fri, 19 Jan 2007, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
On Fri, 19 Jan 2007, Junio C Hamano wrote:
quoted
I still am having a hard time trying to explain what these
commands would do, and why they might be useful:

	git-log --walk-reflogs master..next
I had less problems explaining that when walking fell back to walking the 
parents.

It could even make sense to...
(meaning that is not what the code does...)
quoted
Of course, you could always say: if you ask for strange things, you will 
get strange things.
But if you have to say that, doesn't it suggest that accepting
the option --walk-reflogs when you have anything other than one
single positive commit in revs.pending leads to end user
confusion?
How about failing if there are _uninteresting_ commits? So,

	git log --walk-reflogs next master

still works?

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