Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-28 Thread Junio C Hamano
Stephan Beyer writes: > However, it probably should be documented what "git bisect next" does > after you've specified bad and good commits. > > For that, I'd like to have an extra informational paragraph. > What about: "In general, the command computes the next commit for the > bisection and che

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-27 Thread Stephan Beyer
Hi, On 02/27/2016 07:03 PM, Junio C Hamano wrote: > Stephan Beyer writes: > >> This command is also handy when you accidentally checked out another >> commit during a bisection. It computes the commit for the bisection >> and checks it out again. >> >> -->8-->8-->8-- >> >> Is that better? > > T

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-27 Thread Junio C Hamano
Stephan Beyer writes: > I rephrase it as follows to not encourage checking out another branch > (or commit ;]) but to mention that it works to get back if someone > accidentally did it. > > --8<--8<--8<-- > > Bisect next > ~~~ > > In case you have marked a commit as bad but you do not kno

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-27 Thread Stephan Beyer
Hi, On 02/26/2016 07:47 PM, Junio C Hamano wrote: > But I wonder if it is safe and sane to encourage "checking out other > branches during a bisect session." as you cannot tell what other > crazy things they will do while on "other branches". I do not think > we even try to (and I do not think we

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-26 Thread Junio C Hamano
Stephan Beyer writes: > +Bisect next > +~~~ > + > +Sometimes it can be necessary to check out other branches during a bisect > +session. If you want to check out the next commit of the bisection again, > +simply issue the command: > + > + > +$ git bisect next > +

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-26 Thread Jacob Keller
On Thu, Feb 25, 2016 at 6:04 PM, Stephan Beyer wrote: > This patch considers the source code comment that says to be > "not sure we want 'next' at the UI level anymore", and replies with > "Yes, we want it!". Therefore, the "git bisect next" functionality > is explicitly motivated and documented.

[PATCH 01/16] bisect: write about `bisect next` in documentation

2016-02-25 Thread Stephan Beyer
Mention `bisect next` in the documentation of bisect. `bisect next` is only useful in rare cases and the result can also be accomplished using other utilities (like reflog). However, it is available as a bisect command and should hence be documented. Also mention the use case when no good commit i