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

Re: [PATCH v3 0/5] nd/branch-show-rebase-bisect-state updates

From: Duy Nguyen <hidden>
Date: 2016-06-15 22:56:27

On Wed, Mar 20, 2013 at 1:37 AM, Junio C Hamano [off-list ref] wrote:
I was running "git bisect start pu jch" (jch is a branch I do not
push out everywhere that is somewhere in the middle of
"master..pu"), and then after bisection finished, saw this:

    $ git branch --with 66887099e096f0258a5ef3b1e7458748597bdffe
    * (no branch, bisecting jch)
      nd/magic-pathspecs
      pu

which is obviously bogus.  I only said "I know the tip of pu is bad
and the tip of jch is good".  If anything, I was bisecting the
breakage in 'pu', not in 'jch'.

I think the message should better say "before you started to bisect
you were on 'jch'" or something instead.
How about

* (no branch, bisect started on jch)

then? I don't want to make it too long because it'll waste space in
column layout.
-- 
Duy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help