From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Testers <gdb-testers@sourceware.cygnus.com>
Cc: GDB Discussion <gdb@sourceware.cygnus.com>,
"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: GDB snapshot changes
Date: Mon, 20 Mar 2000 23:36:00 -0000 [thread overview]
Message-ID: <38D72679.BAD97DCD@cygnus.com> (raw)
[Sorry for the cross post. Please set followups to
gdb@sourceware.cygnus.com]
Hello,
Firstly, I'm pleased to report that nightly snapshots appear to be
working reliably. See the directory:
ftp://sourceware.cygnus.com/pub/gdb/snapshots/
For those that are curious, ``-D'' is used so that while each snapshot
is created during the afternoon, it contains the sources from exactly
``00:00 GMT'' each morning.
Secondly, as part of this revamp I've changed what is created. Instead
of a plithera of snapshots and diffs (gdb, insight, dejagnu,
gdb+dejagnu, insight+deajgnu), I'm now only creating snapshots and diffs
for:
gdb+dejagnu
and insight+dejagnu
The rationale for these changes are:
o People using snapshots probably
want to put GDB through its
testsuite before using it...
To do this reliably, a synchronized
gdb and dejagnu are needed.
Combining the two into a single
snapshot should simplify this.
o It reduces greatly the total
amount of data being shaddowed
by remote sites.
Finally, I've seen a request for md5 or brik checksums of all files.
I've added that to my list of things to do.
If people have comments or objections, please let me know.
Andrew
PS: For what its worth, for many years I was dependant on the nightly
snapshots. One frustration I found was the constant need to
download/apply/merge both gdb and dejagnu diffs. Having dejagnu bundled
in with gdb, I think, is much easier. Hopefully others will agree :-)
next reply other threads:[~2000-03-20 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-20 23:36 Andrew Cagney [this message]
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
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=38D72679.BAD97DCD@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-testers@sourceware.cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.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).