From: Junio C Hamano <junkio@cox.net>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] C implementation of the 'git' program, take two.
Date: Tue, 15 Nov 2005 16:17:44 -0800 [thread overview]
Message-ID: <7vmzk5e993.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <437A78FC.10608@op5.se> (Andreas Ericsson's message of "Wed, 16 Nov 2005 01:10:36 +0100")
Andreas Ericsson <ae@op5.se> writes:
> Dunno, really. I suppose it does as it bypasses the shell with the
> execve() call, unless windows or the cygwin stuff does some trickery to
> find an .exe regardless.
>
> Is it ok if I send a separate patch for it, or would you rather have me
> redo this one?
I'll take this as is and have Cygwin folks holler if it breaks
things for them ;-). Thanks.
next prev parent reply other threads:[~2005-11-16 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 23:31 [PATCH 1/3] C implementation of the 'git' program, take two Andreas Ericsson
2005-11-15 23:45 ` Junio C Hamano
2005-11-16 0:10 ` Andreas Ericsson
2005-11-16 0:17 ` Junio C Hamano [this message]
2005-11-16 0:18 ` Linus Torvalds
2005-11-16 0:42 ` Andreas Ericsson
2005-11-16 2:02 ` Linus Torvalds
2005-11-16 2:18 ` Johannes Schindelin
2005-11-16 21:04 ` Alex Riesen
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=7vmzk5e993.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
/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).