git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Chris Wright <chrisw@osdl.org>,
	Fredrik Kuivinen <freku045@student.liu.se>,
	git@vger.kernel.org
Subject: Re: Ship our own copy of subprocess.py
Date: Tue, 20 Sep 2005 10:56:50 -0700	[thread overview]
Message-ID: <43304D62.4010403@zytor.com> (raw)
In-Reply-To: <7vll1s6yao.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Chris Wright <chrisw@osdl.org> writes:
> 
> 
>>Sorry I don't think this one will work.  It's not going to install
>>compat/subprocess.py, and if it did, I don't think it'd be able to import
>>(how will it find subprocess.py?).
> 
> 
> My intent can be found out if you do this:
> 
>     $ make
>     $ diff -u git-merge-recursive.py git-merge-recursive
>     $ grep -C3 GIT_PYTHON_ Makefile
> 

Seems to work as far as I can tell.

	-hpa

      reply	other threads:[~2005-09-20 17:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 19:07 Why does git-core 0.99.7 require python 2.4? H. Peter Anvin
2005-09-19 20:02 ` Fredrik Kuivinen
2005-09-19 20:55   ` Junio C Hamano
2005-09-19 21:00     ` H. Peter Anvin
2005-09-19 21:22       ` Junio C Hamano
2005-09-19 21:33         ` H. Peter Anvin
2005-09-19 21:49         ` H. Peter Anvin
2005-09-19 23:17           ` jepler
2005-09-19 23:24             ` H. Peter Anvin
2005-09-20  2:02               ` Junio C Hamano
2005-09-20  4:39                 ` Ship our own copy of subprocess.py Junio C Hamano
2005-09-20  4:41                   ` H. Peter Anvin
2005-09-20  5:30                   ` Fredrik Kuivinen
2005-09-20 14:55                     ` Linus Torvalds
2005-09-20 17:58                       ` H. Peter Anvin
2005-09-20  6:14                   ` Chris Wright
2005-09-20  6:36                     ` Junio C Hamano
2005-09-20 17:56                       ` H. Peter Anvin [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=43304D62.4010403@zytor.com \
    --to=hpa@zytor.com \
    --cc=chrisw@osdl.org \
    --cc=freku045@student.liu.se \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).