{"thread":{"id":"9309","subject":"Arbitrary long file lists?","startedAt":"2007-07-30T12:33:50Z","lastAt":"2007-07-30T13:18:10Z","messageCount":3,"participants":["David Kastrup","Alex Riesen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"49099","messageId":"866442t6j5.fsf@lola.quinscape.zz","threadId":"9309","inReplyTo":null,"subject":"Arbitrary long file lists?","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-07-30T12:33:50Z","receivedAt":"2007-07-30T12:33:50Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\nHi,\n\ncommands like git-archive take a file list on the command line.  If\nthe number of files does no longer fit the argv limitations, this\ncauses a problem.\n\nSo it might be nice to be able to treat some \"filenames\" in a file\nlist special:\n\n-@=filename (read LF-lines with filenames from filename)\n-@=- (read lines with filenames from stdin)\n-@z=filename (read NUL-terminated list with filenames from filename)\n-@z=- (same from stdin)\n\nOf course, this particular syntax, very loosely inspired by infozip,\nleaves a lot to be desired: prettier proposals welcome.\n\nBut the feature itself would not be unimportant.  I am also fuzzy on\nwhat sort of quoting should be interpreted outside of the\nNUL-terminated case.\n\n-- \nDavid Kastrup\n"},{"id":"49100","messageId":"81b0412b0707300543p48964b73o5f972405645e70e9@mail.gmail.com","threadId":"9309","inReplyTo":"866442t6j5.fsf@lola.quinscape.zz","subject":"Re: Arbitrary long file lists?","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-07-30T12:43:08Z","receivedAt":"2007-07-30T12:43:08Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On 7/30/07, David Kastrup <dak@gnu.org> wrote:\n> commands like git-archive take a file list on the command line.  If\n> the number of files does no longer fit the argv limitations, this\n> causes a problem.\n>\n> So it might be nice to be able to treat some \"filenames\" in a file\n> list special:\n>\n> -@=filename (read LF-lines with filenames from filename)\n> -@=- (read lines with filenames from stdin)\n> -@z=filename (read NUL-terminated list with filenames from filename)\n> -@z=- (same from stdin)\n\ngit-update-index and the like use --stdin and -z.\nWhat do you need the one with filename for?\n"},{"id":"49102","messageId":"86zm1erpwt.fsf@lola.quinscape.zz","threadId":"9309","inReplyTo":"81b0412b0707300543p48964b73o5f972405645e70e9@mail.gmail.com","subject":"Re: Arbitrary long file lists?","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-07-30T13:18:10Z","receivedAt":"2007-07-30T13:18:10Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\"Alex Riesen\" <raa.lkml@gmail.com> writes:\n\n> On 7/30/07, David Kastrup <dak@gnu.org> wrote:\n>> commands like git-archive take a file list on the command line.  If\n>> the number of files does no longer fit the argv limitations, this\n>> causes a problem.\n>>\n>> So it might be nice to be able to treat some \"filenames\" in a file\n>> list special:\n>>\n>> -@=filename (read LF-lines with filenames from filename)\n>> -@=- (read lines with filenames from stdin)\n>> -@z=filename (read NUL-terminated list with filenames from filename)\n>> -@z=- (same from stdin)\n>\n> git-update-index and the like use --stdin and -z.\n> What do you need the one with filename for?\n\nUh, git-archive?\n\nI was thinking that -z could conflict with other uses for in/output,\nbut indeed git-archive does not seem to have any other area that would\nbe affected by -z.\n\nSo this request at the current point of time can be reduced to let\ngit-archive have --stdin and -z options.  That is actually important\nas one can't concatenate zip-files, and so xargs does not help.\n\nBut file lists are also important for things like git-diff (for which\nthe NUL-endedness of input is a separate issue from its output).  So\ninstead of adding stdin piecemeal, it was some sort of idea to have\nthis generally available in file lists.\n\nIf somebody can come up with a nice syntax.\n\n-- \nDavid Kastrup\n"}]}