Re: [PATCH 01/16] bisect: write about `bisect next` in documentation
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Feb 26, 2016, 08:02 UTC
- Message-ID
- <CA+P7+xqRFvzvD3dX+WM9vuJ1mmSdMeoQQTat+4be0gfsLXfSJw@mail.gmail.com>
- In-Reply-To
- <1456452282-10325-2-git-send-email-s-beyer@gmx.net>
On Thu, Feb 25, 2016 at 6:04 PM, Stephan Beyer <s-beyer@gmx.net> wrote:
Show 5 quoted lines
> 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. >
I did not know about this, but I definitely would have found it useful in the past.
Thanks, Jake