From: Jeffrey A Law <law@cygnus.com>
To: Mark Galassi <rosalia@lanl.gov>
Cc: overseers@sourceware.cygnus.com
Subject: Re: disallowing too-long messages
Date: Mon, 22 May 2000 10:32:00 -0000 [thread overview]
Message-ID: <2807.959016135@upchuck> (raw)
Message-ID: <20000522103200.dW9tdoIOBe0h3a3B2dcVBs6Ks9hY8Kvy9Ryj98clzRs@z> (raw)
In-Reply-To: <76itw9q302.fsf@odie.lanl.gov>
In message < 76itw9q302.fsf@odie.lanl.gov >you write:
>
> 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.
>
> Is it possible with our ezlm s/w?
It's trivial. Presumably a 100kbyte limit on gsl-discuss and gsl-announce
would be appropriate?
jeff
next prev parent reply other threads:[~2000-05-22 10:32 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 ` Jim Kingdon
2000-05-20 10:26 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-05-20 11:33 ` Jason Molenda
2000-12-30 6:08 ` Jeffrey A Law [this message]
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
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=2807.959016135@upchuck \
--to=law@cygnus.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).