All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Tapsell <johnflux@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ealdwulf Wuffinga <ealdwulf@googlemail.com>,
	Christian Couder <chriscool@tuxfamily.org>,
	Git List <git@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Generalised bisection
Date: Wed, 11 Mar 2009 12:08:10 +0000	[thread overview]
Message-ID: <43d8ce650903110508o3d12f32m8202fae750d215a@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903111304520.10279@pacific.mpi-cbg.de>

2009/3/11 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> Hi,
>
> On Wed, 11 Mar 2009, John Tapsell wrote:
>
>> 2009/3/11 Ealdwulf Wuffinga <ealdwulf@googlemail.com>:
>> > On Tue, Mar 10, 2009 at 7:08 AM, Christian Couder
>> > <chriscool@tuxfamily.org> wrote:
>> >
>> >> I will try to have a look at the end of this week.
>> >> But do you want it to be integrated with Git or do you want it to be an
>> >> independant project that works with many different version control system?
>> >
>> > Hmm. Whatever works, I guess. On the one hand the code does seem
>> > naturally generic. On the other hand, it's good if users don't
>> > have to separately obtain an extra package to use it. Supposing that
>> > the algorithm proves useful, would the git project  be okay with an
>> > extra dependency, or would you want to integrate it? Right now it's in
>> > python, which I understand is an obstacle to integration.
>>
>> There used to be a dependency on python.  git-merge-recursive for
>> example, before it was converted to C.
>
> Not "for example".  It was the only dependency of git.git on Python, and
> the rewrite of merge-recursive was only done to break that dependency, as
> I had a platform where I could not install Python.

But installing perl was no problem?  (Just curious)

John

  reply	other threads:[~2009-03-11 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  1:40 Generalised bisection Ealdwulf Wuffinga
2009-03-10  7:08 ` Christian Couder
2009-03-11  8:59   ` Ealdwulf Wuffinga
2009-03-11  9:35     ` John Tapsell
2009-03-11 12:05       ` Johannes Schindelin
2009-03-11 12:08         ` John Tapsell [this message]
2009-03-11 13:04           ` Johannes Schindelin
2009-03-11 13:24             ` John Tapsell
2009-03-11 22:14               ` Ealdwulf Wuffinga
2009-03-11 22:15       ` Ealdwulf Wuffinga
2009-03-12  6:45         ` John Tapsell
2009-03-12 10:55           ` Johannes Schindelin
2009-03-12 18:02             ` Steven Tweed
2009-03-13 10:00               ` Ealdwulf Wuffinga
2009-03-13 12:49               ` Ealdwulf Wuffinga
2009-03-13 15:19                 ` Steven Tweed
2009-03-15 19:16                   ` Ealdwulf Wuffinga
2009-03-16 10:29                     ` Steven Tweed
2009-03-16 10:37                       ` John Tapsell
2009-03-16 22:47                         ` Ealdwulf Wuffinga
2009-03-16 22:08                       ` Ealdwulf Wuffinga
2009-03-13  9:58           ` Ealdwulf Wuffinga
2009-03-13 10:55             ` Johannes Schindelin
2009-03-13 12:42               ` John Tapsell
2009-03-13 13:56                 ` Johannes Schindelin

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=43d8ce650903110508o3d12f32m8202fae750d215a@mail.gmail.com \
    --to=johnflux@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=ealdwulf@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.