From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: Arbitrary long file lists?
Date: Mon, 30 Jul 2007 15:18:10 +0200 [thread overview]
Message-ID: <86zm1erpwt.fsf@lola.quinscape.zz> (raw)
In-Reply-To: 81b0412b0707300543p48964b73o5f972405645e70e9@mail.gmail.com
"Alex Riesen" <raa.lkml@gmail.com> writes:
> On 7/30/07, David Kastrup <dak@gnu.org> wrote:
>> commands like git-archive take a file list on the command line. If
>> the number of files does no longer fit the argv limitations, this
>> causes a problem.
>>
>> So it might be nice to be able to treat some "filenames" in a file
>> list special:
>>
>> -@=filename (read LF-lines with filenames from filename)
>> -@=- (read lines with filenames from stdin)
>> -@z=filename (read NUL-terminated list with filenames from filename)
>> -@z=- (same from stdin)
>
> git-update-index and the like use --stdin and -z.
> What do you need the one with filename for?
Uh, git-archive?
I was thinking that -z could conflict with other uses for in/output,
but indeed git-archive does not seem to have any other area that would
be affected by -z.
So this request at the current point of time can be reduced to let
git-archive have --stdin and -z options. That is actually important
as one can't concatenate zip-files, and so xargs does not help.
But file lists are also important for things like git-diff (for which
the NUL-endedness of input is a separate issue from its output). So
instead of adding stdin piecemeal, it was some sort of idea to have
this generally available in file lists.
If somebody can come up with a nice syntax.
--
David Kastrup
prev parent reply other threads:[~2007-07-30 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 12:33 Arbitrary long file lists? David Kastrup
2007-07-30 12:43 ` Alex Riesen
2007-07-30 13:18 ` David Kastrup [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=86zm1erpwt.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--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