git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
	Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ed Avis <ed.avis@qmaw.com>, git <git@vger.kernel.org>,
	"Miriam R." <mirucam@gmail.com>
Subject: Re: Feature request: 'git bisect run' option to redundantly check start and end commits
Date: Sat, 19 Dec 2020 05:39:38 -0600	[thread overview]
Message-ID: <5fdde67aa2e2e_1de0de208db@natae.notmuch> (raw)
In-Reply-To: <CAP8UFD3AHZppV2puere=zKyRjHhywCYQcO6q4yU7jJCfF0HZJg@mail.gmail.com>

Christian Couder wrote:
> On Fri, Dec 18, 2020 at 6:15 PM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> >
> > Christian Couder wrote:
> > > On Fri, Dec 18, 2020 at 4:39 PM Felipe Contreras
> > > <felipe.contreras@gmail.com> wrote:
> > > > Here's a quick patch to implement such feature (it doesn't apply
> > > > directly, it's mostly for human eyes).
> > >
> > > There has been a lot of work over the years to port code from shell in
> > > git-bisect.sh to C in builtin/bisect--helper.c. So it would be nice,
> > > if you plan to implement this feature, if you could do it directly in
> > > builtin/bisect--helper.c.
> >
> > Yeah, I'm aware and I might be willing to do that--which probably would
> > require moving the whole of "bisect run" to C--if there was an
> > indication that such a patch would actually be merged.
> 
> I think it would likely be merged, as it would just be finishing the
> porting git bisect to C saga.

My experience tells me otherwise. We'll see.

-- 
Felipe Contreras

  reply	other threads:[~2020-12-19 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 12:22 Feature request: 'git bisect run' option to redundantly check start and end commits Ed Avis
2020-12-18 15:35 ` Felipe Contreras
2020-12-18 16:16   ` Christian Couder
2020-12-18 17:15     ` Felipe Contreras
2020-12-19  7:46       ` Christian Couder
2020-12-19 11:39         ` Felipe Contreras [this message]
2020-12-19 17:31         ` Junio C Hamano

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=5fdde67aa2e2e_1de0de208db@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=ed.avis@qmaw.com \
    --cc=git@vger.kernel.org \
    --cc=mirucam@gmail.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;
as well as URLs for NNTP newsgroup(s).