git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Ealdwulf Wuffinga <ealdwulf@googlemail.com>
Cc: Clemens Buchacher <drizzd@aon.at>,
	Christian Couder <chriscool@tuxfamily.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: RFE: "git bisect reverse"
Date: Fri, 29 May 2009 16:20:31 +1200	[thread overview]
Message-ID: <4A1F628F.9010407@vilain.net> (raw)
In-Reply-To: <efe2b6d70905281329s1ae5a94coe5875714f341d5a9@mail.gmail.com>

Ealdwulf Wuffinga wrote:
>> Sounds like interesting stuff, can you make a patch out of it?
>>     
>
> The code as it stands will actually work with an unmodified git.
> What it doesn't yet have is a 'git-bisect'-like frontend, which is the only
> part which would actually require modifying (or just adding to) git itself.
>
> It does already interface to the git plumbing, so you can try it out if you
> don't mind using a slightly ungitlike  interface.
>
> I assume it's not worth doing a patch which would just copy my tree
> into the git source tree?
>
> There was also, last time I mentioned this on the list, some question
> as to whether it was acceptable to add something written in python to
> git.
>   

I mean, can you port your algorithm from python to the git-bisect C
source and therefore make something of benefit to existing 'git bisect'
users ?

Sam.

  reply	other threads:[~2009-05-29  4:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 22:21 RFE: "git bisect reverse" H. Peter Anvin
2009-05-27  3:00 ` Sam Vilain
2009-05-27  4:20   ` H. Peter Anvin
2009-05-27  5:26     ` Christian Couder
2009-05-27 21:11       ` Ealdwulf Wuffinga
2009-05-27 21:18         ` Clemens Buchacher
2009-05-27 22:07           ` Ealdwulf Wuffinga
2009-05-27 23:08             ` Sam Vilain
2009-05-28 20:29               ` Ealdwulf Wuffinga
2009-05-29  4:20                 ` Sam Vilain [this message]
2009-05-31 22:41                   ` Ealdwulf Wuffinga
2009-05-28  3:11             ` H. Peter Anvin
2009-05-28 21:07               ` Ealdwulf Wuffinga
2009-05-28 21:54                 ` H. Peter Anvin
2009-05-31 22:18                   ` Ealdwulf Wuffinga
2009-05-27 20:11   ` Christian Couder
2009-05-27  8:22 ` Nanako Shiraishi
2009-05-27 20:26   ` Matthieu Moy

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=4A1F628F.9010407@vilain.net \
    --to=sam@vilain.net \
    --cc=chriscool@tuxfamily.org \
    --cc=drizzd@aon.at \
    --cc=ealdwulf@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.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).