public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: "Dave Korn" <dk@artimi.com>, <gcc@gcc.gnu.org>,
	<overseers@sources.redhat.com>
Subject: Re: Protocol error: too many arguments
Date: Tue, 12 Oct 2004 13:43:00 -0000	[thread overview]
Message-ID: <16747.57120.225722.754191@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <m3u0t0m51d.fsf@gossamer.airs.com>

Ian Lance Taylor writes:
 > Andrew Haley <aph@redhat.com> writes:
 > 
 > > Dave Korn writes:
 > >  > > -----Original Message-----
 > >  > > From: gcc-owner On Behalf Of Andrew Haley
 > >  > > Sent: 12 October 2004 14:10
 > >  > 
 > >  > > Despite doing my branch commit in individual directories rather than
 > >  > > top level, I got this message again today:
 > >  > > 
 > >  > > Protocol error: too many arguments
 > >  > > 
 > >  > > Last time I saw this error it resulted in corrupted attr files on the
 > >  > > server.
 > >  > > 
 > >  > > I'll try a fresh checkout once my commit is done.
 > >  > 
 > >  >   Should probably Cc overseers, as a heads-up.
 > > 
 > > Any mail I send to overseers bounces.
 > > 
 > > I wonder if anyone knows exactly what the limit is.  I'm guessing it's
 > > maybe a postcommit script that hits a kernel limit on the number of
 > > arguments to a command.
 > 
 > Current versions of the CVS server only accepts up to 10000 files in a
 > single commit.  I think this is a misguided attempt to limit memory
 > usage in the server.

10,000 files!  Eek!  Well, I didn't think I was committing that many.

Is that what the "Protocol error: too many arguments" message refers
to, do you know?

Andrew.

  reply	other threads:[~2004-10-12 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16747.55189.754030.610553@cuddles.cambridge.redhat.com>
2004-10-12 13:17 ` Dave Korn
2004-10-12 13:21   ` Andrew Haley
2004-10-12 13:38     ` Ian Lance Taylor
2004-10-12 13:43       ` Andrew Haley [this message]
2004-10-13  2:27         ` Ian Lance Taylor
2004-10-12 14:14     ` Dave Korn
2004-10-12 14:30       ` Christopher Faylor
2004-10-12 14:36         ` Andrew Haley
2004-10-12 15:20           ` Dave Korn
2004-10-12 21:55             ` Phil Edwards

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=16747.57120.225722.754191@cuddles.cambridge.redhat.com \
    --to=aph@redhat.com \
    --cc=dk@artimi.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=overseers@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).