public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: web/2493: GNATSweb should discourage huge attachments
Date: Thu, 05 Apr 2001 09:56:00 -0000 [thread overview]
Message-ID: <E14lCvA-000706-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 2493
>Category: web
>Synopsis: GNATSweb should discourage huge attachments
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: gerald
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Apr 05 09:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.0 20010405 (prerelease)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:
Sometimes people submit huge attachments via GNATSweb, which then get
sent to gcc-prs. It would be nice if some heuristics could be applied
to discourage such attachments when they are larger than necessary.
Examples of inappropriate usages:
* Attaching a multimegabyte source tarball rather than the individual
preprocessed file that is relevant.
* Attaching a huge uncompressed .i or .ii file instead of a compressed
version.
>How-To-Repeat:
Observe that unnecessarily multimegabyte messages arrive at gcc-prs
from time to time (e.g. a 6 Mbyte one today). They don't arrive at
gcc-bugs because of the message size limit on that list, so not many
people will see them.
>Fix:
If someone tries to submit a large tarball, ask them "are you sure"
before accepting the PR. If someone submits a large file which bzip2
or gzip reduces in size substantially, silently compress it with bzip2
or gzip (adjusting the name accordingly) before attaching it to the
new PR. (Since GNATSweb attachments don't appear as MIME attachments
in the mailing list messages and so need some manual decoding, this
doesn't significantly affect the usability of the message to gcc-prs.)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-04-05 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 9:56 Joseph Myers [this message]
2001-06-12 5:13 gerald
2003-03-15 18:32 bangerth
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=E14lCvA-000706-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@gcc.gnu.org \
/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).