From: Jim Kingdon <kingdon@redhat.com>
To: rosalia@lanl.gov
Cc: overseers@sourceware.cygnus.com
Subject: Re: disallowing too-long messages
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200005201726.NAA04957@devserv.devel.redhat.com> (raw)
In-Reply-To: <76itw9q302.fsf@odie.lanl.gov>
> One of my GSL maintainers wrote this and it seems reasonable: it would
> suck if someone were to inadvertently post a 5meg "make check" output.
Most lists probably have a 5 meg limit, as described at
http://sourceware.cygnus.com/sourceware/procedures/new-list.txt
Yes, ideally project leaders would be able to change the limit at
will. But failing that, I'm not sure I want to get into the game of
"what should the limit be" for each list as I'm sure there are lots of
opinions (and there are lots of lists, that's for sure).
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@redhat.com>
To: rosalia@lanl.gov
Cc: overseers@sourceware.cygnus.com
Subject: Re: disallowing too-long messages
Date: Sat, 20 May 2000 10:26:00 -0000 [thread overview]
Message-ID: <200005201726.NAA04957@devserv.devel.redhat.com> (raw)
Message-ID: <20000520102600.ypjLJlIevEr_wwHpURgQprK92ErUJWLKKdvbAwIOl-A@z> (raw)
In-Reply-To: <76itw9q302.fsf@odie.lanl.gov>
> One of my GSL maintainers wrote this and it seems reasonable: it would
> suck if someone were to inadvertently post a 5meg "make check" output.
Most lists probably have a 5 meg limit, as described at
http://sourceware.cygnus.com/sourceware/procedures/new-list.txt
Yes, ideally project leaders would be able to change the limit at
will. But failing that, I'm not sure I want to get into the game of
"what should the limit be" for each list as I'm sure there are lots of
opinions (and there are lots of lists, that's for sure).
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Mark Galassi
2000-05-19 21:06 ` Mark Galassi
2000-12-30 6:08 ` Jeffrey A Law
2000-05-22 10:32 ` Jeffrey A Law
2000-12-30 6:08 ` Mark Galassi
2000-05-22 10:38 ` Mark Galassi
2000-12-30 6:08 ` Jeffrey A Law
2000-05-22 10:50 ` Jeffrey A Law
2000-12-30 6:08 ` Jim Kingdon [this message]
2000-05-20 10:26 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-05-20 11:33 ` Jason Molenda
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=200005201726.NAA04957@devserv.devel.redhat.com \
--to=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.com \
--cc=rosalia@lanl.gov \
/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).