From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: old GDB snapshots...
Date: Thu, 13 Dec 2012 12:44:00 -0000 [thread overview]
Message-ID: <20121213124345.GJ3663@adacore.com> (raw)
Hello all,
Jan was asking about the snaphots we provide on sourceware's
FTP server. And indeed, we have many!
We produce weekly snaphots, and daily patches, I believe.
As far as I can tell, the scripts are supposed to delete old
snapshots, only keeping a certain number of every kind (numbers
depend on the type of file - for instance we keep more daily
diffs than we keep weekly tarballs).
I believe that the scripts do not delete old snapshots after
we increment the version number, so old snapshots have been
accumulating:
- HEAD snapshots: 1.2GB with ~230 files;
- branch snapshots: 3.6GB with ~630 files.
(we have snapshots dating back to 6.3)
I am going to do some cleanup, but how far back do we want
to keep?
Thanks,
--
Joel
next reply other threads:[~2012-12-13 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 12:44 Joel Brobecker [this message]
2012-12-13 13:48 ` Mark Kettenis
2012-12-13 13:52 ` Joel Brobecker
2012-12-13 13:54 ` Jan Kratochvil
2012-12-21 7:37 ` Joel Brobecker
2012-12-21 16:04 ` Jan Kratochvil
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=20121213124345.GJ3663@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.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