From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: rganesan@myrealbox.com, insight@sourceware.cygnus.com,
gdb@sourceware.cygnus.com
Subject: Re: GDB snapshot changes
Date: Mon, 03 Apr 2000 17:11:00 -0000 [thread overview]
Message-ID: <38E932C8.C3EBA163@cygnus.com> (raw)
In-Reply-To: <200004030847.EAA11826@indy.delorie.com>
Eli Zaretskii wrote:
>
> > In addition, starting tomorrow the nightly snapshots will include md5
> > sums.
>
> This md5 file turns out to be quite a pest. About 90% of each
> *diff.bz2 file is devoted to this file alone, which bloats the diffs
> tremendously. Some of us have a slow modem to fetch the files, so
> each KB counts...
>
> Is it possible to just put md5 on sourceware, for those who need it,
> and remove it from the diffs?
This sounds wrong. Hmm, wonder if the process I used to order the md5
file was stable :-/
Andrew
next prev parent reply other threads:[~2000-04-03 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-20 23:36 Andrew Cagney
2000-03-21 2:42 ` Ganesan R
2000-03-21 21:14 ` Andrew Cagney
2000-03-28 22:51 ` Andrew Cagney
2000-04-03 1:47 ` Eli Zaretskii
2000-04-03 17:11 ` Andrew Cagney [this message]
2000-04-03 21:32 ` Andrew Cagney
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=38E932C8.C3EBA163@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=rganesan@myrealbox.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).