git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-svnimport.perl: fix for 'arg list too long...'

From
Junio C Hamano <junkio@cox.net>
Date
Feb 1, 2006, 20:27 UTC
Message-ID
<7v64nybz9m.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060201155331.GE18078@sashak.voltaire.com>
Sasha Khapyorsky <sashak@voltaire.com> writes:
> This fixes 'arg list too long..' problem with git-ls-files.

I wonder if feeding the list into a pipe to 'update-index --stdin' would be an option.

BTW, please do not do this:
        Mail-Followup-To: Junio C Hamano <junkio@cox.net>,
                Matthias Urlichs <smurf@smurf.noris.de>, git@vger.kernel.org
It is simply rude.
 * I and/or Smurf may be uninterested in hearing the whole
   discussion thread started by you.  We might well be, but that
   is not something you shoudl decide upfront in your message.
 * When a recipient of your message tries to "[R]eply" to *you*,
   that Mail-Followup-To: would cause the MUA to address that
   message to me and/or smurf by default, not to you.  I had to
   edit the resulting To: header by hand to address this
   response to you.  Why force extra work on others?

I know why you did it --- you subscribe to git list and otherwise you would get two copies.

That is _not_ a good excuse. That is how mailing lists work; either you filter the duplicates on your end, or you learn to live with it. Please don't force extra work on others.

I think the only header mucking of this kind that is acceptable is to remove yourself from CC: line when the mailing list you subscribe to is already on the CC: line.

Previous: Sasha KhapyorskyNext: Sasha Khapyorsky
Message 2 of 6 in “git-svnimport.perl: fix for 'arg list too long...'”
  1. git-svnimport.perl: fix for 'arg list too long...'Sasha Khapyorsky, Feb 1, 2006
  2. Junio C HamanoFeb 1, 2006
  3. Sasha KhapyorskyFeb 1, 2006
  4. Junio C HamanoFeb 1, 2006
  5. Matthias UrlichsFeb 1, 2006
  6. Sasha KhapyorskyFeb 2, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.