Re: [PATCH] bisect: print abbrev sha1 for first bad commit

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

Re: [PATCH] bisect: print abbrev sha1 for first bad commit

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:04:43

Jeff King [off-list ref] writes:
I'd argue for simply never showing the diff (dropping the "opt.diff = 1"
line from bisect.c:show_diff_tree), but that is mostly my personal
opinion.
Yeah, I think that is sensible. It may even be OK to just give a
"log --oneline".  

Re: [PATCH] bisect: print abbrev sha1 for first bad commit

From: Christian Couder <hidden>
Date: 2016-06-15 23:04:43

On Mon, May 11, 2015 at 6:33 AM, Junio C Hamano [off-list ref] wrote:
Jeff King [off-list ref] writes:
quoted
I'd argue for simply never showing the diff (dropping the "opt.diff = 1"
line from bisect.c:show_diff_tree), but that is mostly my personal
opinion.
Yeah, I think that is sensible. It may even be OK to just give a
"log --oneline".
Or maybe we could let the user configure the diff options or even the
command used when the first bad commit is found?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help