From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>, Johan Herland <johan@herland.net>,
Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] tests: handle NO_PYTHON setting
Date: Mon, 30 Nov 2009 08:55:51 +0100 [thread overview]
Message-ID: <fabb9a1e0911292355v260b9f0ck79d993e25f0c5c61@mail.gmail.com> (raw)
In-Reply-To: <20091130075221.GA5421@coredump.intra.peff.net>
Heya,
On Mon, Nov 30, 2009 at 08:52, Jeff King <peff@peff.net> wrote:
> This feels a little funny for NO_PYTHON to mean "no remote helpers at
> all". But that is the way the Makefile is set up, since we seem to have
> only python helpers.
I don't understand what you mean? Do you mean NO_PYTHON implies "no
remote helpers at all", or "not having any remote helpers" implies
NO_PYTHON? Either way, I'm not sure how to set it up differently, not
having that much Makefile foo myself, so maybe Johan and Daniel could
comment?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-11-30 7:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 7:52 [PATCH] tests: handle NO_PYTHON setting Jeff King
2009-11-30 7:55 ` Sverre Rabbelier [this message]
2009-11-30 7:59 ` Jeff King
2009-11-30 8:04 ` Sverre Rabbelier
2009-11-30 8:05 ` Jeff King
2009-11-30 8:28 ` Junio C Hamano
2009-11-30 8:35 ` Sverre Rabbelier
2009-11-30 8:49 ` Junio C Hamano
2009-11-30 9:56 ` Sverre Rabbelier
2009-11-30 10:59 ` Johan Herland
2009-11-30 17:27 ` Junio C Hamano
2009-11-30 18:01 ` Johan Herland
2009-11-30 18:07 ` Brandon Casey
2009-11-30 20:54 ` Jeff King
2009-11-30 21:17 ` Brandon Casey
2009-11-30 22:31 ` Johan Herland
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=fabb9a1e0911292355v260b9f0ck79d993e25f0c5c61@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--cc=peff@peff.net \
/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).