git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "R. Tyler Ballance" <tyler@monkeypox.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] Correct references to /usr/bin/python which does not exist on FreeBSD
Date: Sun, 21 Mar 2010 16:00:06 -0700	[thread overview]
Message-ID: <20100321230006.GC32016@kiwi.sharlinx.com> (raw)
In-Reply-To: <7veijdfhmm.fsf@alter.siamese.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]


On Sun, 21 Mar 2010, Junio C Hamano wrote:

> "R. Tyler Ballance" <tyler@monkeypox.org> writes:
> 
> >> I would have expected that the patch would look more like this:
> >> ...
> >> What am I missing?
> >
> > No, that looks right, I didn't notice the specialized section towards the
> > bottom for FreeBSD or the others for that matter.
> 
> Thanks.  I usually use a "make" wrapper to handle platform particulars
> like setting PYTHON_PATH automatically outside of the build system we
> ship, and never noticed this.
> 
> I'll just commit my version with a forged sign-off from you ;-)

I find these terms acceptable :)


Cheers,
-R. Tyler Ballance
--------------------------------------
 Jabber: rtyler@jabber.org
 GitHub: http://github.com/rtyler
Twitter: http://twitter.com/agentdero
   Blog: http://unethicalblogger.com


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-03-21 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 19:01 [PATCH v2] Correct references to /usr/bin/python which does not exist on FreeBSD R. Tyler Ballance
2010-03-21 21:15 ` Junio C Hamano
2010-03-21 21:23   ` R. Tyler Ballance
2010-03-21 22:13     ` Junio C Hamano
2010-03-21 23:00       ` R. Tyler Ballance [this message]

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=20100321230006.GC32016@kiwi.sharlinx.com \
    --to=tyler@monkeypox.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).