From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: git bisect enhancements?
Date: Wed, 30 Nov 2005 14:04:46 -0800 [thread overview]
Message-ID: <7vu0dtokqp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1133386585.30767.34.camel@cashmere.sps.mot.com> (Jon Loeliger's message of "Wed, 30 Nov 2005 15:36:26 -0600")
Jon Loeliger <jdl@freescale.com> writes:
> ... I want to "bump" the bisect point
> up two commits and _then_ build.
>
> So, I'm proposing something like:
>
> $ git bisect bump +<n>
> $ git bisect bump -<n>
>
> To move the bisection point "up" or "down" a commit chain.
Hmph. Doesn't "bisect good" or "bisect bad" let you explicitly
say which one is good or bad, instead of just taking what it
suggests as the next midpoint?
next prev parent reply other threads:[~2005-11-30 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 21:36 git bisect enhancements? Jon Loeliger
2005-11-30 22:04 ` Junio C Hamano [this message]
2005-11-30 22:07 ` Jon Loeliger
2005-11-30 22:23 ` Junio C Hamano
2005-11-30 22:43 ` Junio C Hamano
2005-11-30 23:32 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vu0dtokqp.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox