From: Shawn Pearce <spearce@spearce.org>
To: Christopher Faylor <me@cgf.cx>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Teach git-checkout-index to read filenames from stdin.
Date: Wed, 1 Mar 2006 12:56:06 -0500 [thread overview]
Message-ID: <20060301175606.GA4190@spearce.org> (raw)
In-Reply-To: <20060301155053.GC1010@trixie.casa.cgf.cx>
Christopher Faylor <me@cgf.cx> wrote:
> AFAIK, the length of the command line for cygwin apps is very large --
> if you're using recent versions of Cygwin. I believe that it is longer
> than the linux default. We bypass the Windows mechanism for setting the
> command line when a cygwin program starts a cygwin program.
>
> For native Windows programs, the command line length is ~32K but I don't
> think that git uses any native Windows programs, does it?
No. Currently GIT is entirely dependent on Cygwin. So GIT
wouldn't bump into the ~32K limit due to the cygwin-cygwin feature
you mention. But thanks for the information. I had thought I had
read somewhere in the Cygwin documentation that the command line
length was rather limited (even under cygwin-cygwin calls). Maybe
I was just seeing things. :-)
But even if we can get a long set of args into git-checkout-index its
probably still better to stream them as you can get both programs
working at the same time (rather than waiting for xargs to build
the argument buffer) and you are saving yourself at least one fork
as you don't need to start xargs just to feed git-checkout-index.
Even on Linux where fork is cheap, that's still soemething saved.
--
Shawn.
next prev parent reply other threads:[~2006-03-01 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 2:43 [PATCH] Teach git-checkout-index to read filenames from stdin Shawn Pearce
2006-03-01 15:50 ` Christopher Faylor
2006-03-01 17:56 ` Shawn Pearce [this message]
2006-03-02 13:12 ` Alex Riesen
2006-03-02 13:14 ` 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=20060301175606.GA4190@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=me@cgf.cx \
/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).