From: Daniel Berlin <dberlin@dberlin.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Segher Boessenkool <segher@koffie.nl>, gcc <gcc@gcc.gnu.org>
Subject: Re: A few suggestions for bugzilla mail to gcc-bugs
Date: Mon, 02 Jun 2003 21:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.56.0306021720260.21428@dberlin.org> (raw)
In-Reply-To: <jek7c4gsg4.fsf@sykes.suse.de>
On Mon, 2 Jun 2003, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> |> Can you query the compressed size more quickly? We don't need to be
> |> precise here...
>
> "gzip -l" should do the trick, provided that the input is seekable.
This isn't shell script, it's perl, forking a new process in a very often
used cgi script for every single attachment is *not* a good idea.
But that's besides the point anyway.
The data is *not* in gzip format in memory.
It has no gzip header with the size in it in front.
The *only* way to get the size is to decompress it.
I could, of course, convert them all to be in-memory gzip files, but i'm a
bit busy with other things at the moment to care about this.
:)
next prev parent reply other threads:[~2003-06-02 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 2:02 Segher Boessenkool
2003-05-24 2:14 ` Daniel Berlin
2003-05-24 2:56 ` Daniel Jacobowitz
2003-05-24 3:05 ` Daniel Berlin
2003-05-24 3:09 ` DJ Delorie
2003-05-24 3:57 ` Daniel Berlin
2003-05-24 15:15 ` Daniel Jacobowitz
2003-06-02 20:02 ` Andreas Schwab
2003-06-02 21:34 ` Daniel Berlin [this message]
2003-06-02 21:38 ` Daniel Jacobowitz
2003-06-02 21:54 ` Daniel Berlin
2003-06-02 22:03 ` Daniel Jacobowitz
2003-05-24 3:42 ` Segher Boessenkool
2003-05-24 9:52 ` Joseph S. Myers
2003-05-24 15:46 ` Daniel Berlin
2003-05-24 20:17 ` Joseph S. Myers
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=Pine.LNX.4.56.0306021720260.21428@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
--cc=segher@koffie.nl \
/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).