Re: [PATCH] Documentation: bisect: "start" accepts one bad and many good commits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Christian Couder <chriscool@xxxxxxxxxxxxx> writes:

> Signed-off-by: Christian Couder <chriscool@xxxxxxxxxxxxx>

Thanks.

> +If you know beforehand more than one good commits, you can narrow the
> +bisect space down without doing the whole tree checkout every time you
> +give good commits. You give the bad revision immediately after `start`
> +and then you give all the good revisions you have:
> +
> +------------
> +$ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 --
> +                   # v2.6.20-rc6 is bad
> +                   # v2.6.20-rc4 and v2.6.20-rc1 are good
>  ------------

We would probably want mnemonic to help people remember the
order of parameters: Bad comes before Good, simply because B
sorts earlier than G.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]