All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Fredrik Kuivinen <freku045@student.liu.se>, git@vger.kernel.org
Subject: Re: Ship our own copy of subprocess.py
Date: Mon, 19 Sep 2005 21:41:16 -0700	[thread overview]
Message-ID: <432F92EC.40007@zytor.com> (raw)
In-Reply-To: <7vfys0cpyj.fsf_-_@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Junio C Hamano <junkio@cox.net> writes:
> 
> 
>> - merge-recursive not requiring 2.4 but checking the result
>>   from 'import subprocess', and optionally install its own
>>   subprocess.py (I could do this myself but Fredrik could help
>>   me);
> 
> 
> I'll be cutting 0.99.7a with this, to help RHEL instalation.
> Proofreading appreciated.
> 

Let me know when you've checked it into the repository, and I'll try 
running "make rpm" on the affected systems.

	-hpa

  reply	other threads:[~2005-09-20  4:41 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 [this message]
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

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=432F92EC.40007@zytor.com \
    --to=hpa@zytor.com \
    --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 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.