Theodore Ts'o writes:
> On Sun, Nov 12, 2017 at 03:21:57PM +0100, Christian Couder wrote:
>>
>> Yeah I agree that it might be something interesting for the user to do.
>> But in this case the sequence in which you give the good and the bad
>> commits is not important.
>> Only the
Hi,
On 11/11/2017 03:38 PM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day
>> wrote:
>>>
>>> the man page for "git bisect" makes no mention of "git bisect next",
>>> but the script
On Sun, Nov 12, 2017 at 03:21:57PM +0100, Christian Couder wrote:
>
> Yeah I agree that it might be something interesting for the user to do.
> But in this case the sequence in which you give the good and the bad
> commits is not important.
> Only the last bad commit and the set of good commits
On Sun, Nov 12, 2017 at 2:43 AM, Junio C Hamano wrote:
> Theodore Ts'o writes:
>
>> On Sat, Nov 11, 2017 at 11:38:23PM +0900, Junio C Hamano wrote:
>>>
>>> Thanks for saving me time to explain why 'next' is still a very
>>> important command but the end users do
"Robert P. J. Day" writes:
>> This reminds me; is there a way to suppress it because I'm about to
>> give a large set of good and bit commits (perhaps because I'm
>
>> replaying part of a git biset log, minus one or two lines that
On Sat, 11 Nov 2017, Theodore Ts'o wrote:
> On Sat, Nov 11, 2017 at 11:38:23PM +0900, Junio C Hamano wrote:
> >
> > Thanks for saving me time to explain why 'next' is still a very
> > important command but the end users do not actually need to be
> > strongly aware of it, because most commands
Theodore Ts'o writes:
> On Sat, Nov 11, 2017 at 11:38:23PM +0900, Junio C Hamano wrote:
>>
>> Thanks for saving me time to explain why 'next' is still a very
>> important command but the end users do not actually need to be
>> strongly aware of it, because most commands
On Sat, Nov 11, 2017 at 11:38:23PM +0900, Junio C Hamano wrote:
>
> Thanks for saving me time to explain why 'next' is still a very
> important command but the end users do not actually need to be
> strongly aware of it, because most commands automatically invokes it
> as their final step due to
Christian Couder writes:
> On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day
> wrote:
>>
>> the man page for "git bisect" makes no mention of "git bisect next",
>> but the script git-bisect.sh does:
>
> Yeah the following patch was related:
On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day
wrote:
>
> the man page for "git bisect" makes no mention of "git bisect next",
> but the script git-bisect.sh does:
Yeah the following patch was related:
the man page for "git bisect" makes no mention of "git bisect next",
but the script git-bisect.sh does:
#!/bin/sh
USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|replay|log|run]'
LONG_USAGE='git bisect help
print
11 matches
Mail list logo