Andy Lutomirski writes:
> Anyway, the idea of merging test commits up to some lowest common
> denominator seems generally useful to me, and the idea of specifying a
> 'prepare the checked-out tree' (as you suggested, where 'git merge
> --no-commit whatever' would be specified) would also be handy
On Mon, Jan 4, 2016 at 12:31 PM, Junio C Hamano wrote:
> Andy Lutomirski writes:
>
>> git bisect run is great, but it's not so great when the test process
>> is "sudo make modules_install && sudo make install && reboot", then
>> boot new kernel, then run emacs, then see if it worked... There
>>
Andy Lutomirski writes:
> git bisect run is great, but it's not so great when the test process
> is "sudo make modules_install && sudo make install && reboot", then
> boot new kernel, then run emacs, then see if it worked... There
> doesn't appear to be a 'git bisect run' option to pause and wai
On Wed, Dec 30, 2015 at 12:09 PM, Junio C Hamano wrote:
> Andy Lutomirski writes:
>
>> I'm currently bisecting a Linux bug on my laptop. The starting good
>> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7.
>> Unfortunately, anything much older than v4.4-rc3 doesn't boot at all.
>>
>>
Andy Lutomirski writes:
> I'm currently bisecting a Linux bug on my laptop. The starting good
> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7.
> Unfortunately, anything much older than v4.4-rc3 doesn't boot at all.
>
> I'd like to say:
>
> $ git bisect merge-to v4.4-rc3
>
> or simil
Hi,
On Wed, Dec 30, 2015 at 11:40 AM, Andy Lutomirski wrote:
> Hi-
>
> I'm currently bisecting a Linux bug on my laptop. The starting good
> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7.
> Unfortunately, anything much older than v4.4-rc3 doesn't boot at all.
>
> I'd like to say:
>
6 matches
Mail list logo
