From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb@sourceware.org
Subject: Re: old GDB snapshots...
Date: Thu, 13 Dec 2012 13:54:00 -0000 [thread overview]
Message-ID: <20121213135429.GA13441@host2.jankratochvil.net> (raw)
In-Reply-To: <201212131347.qBDDlp31015431@glazunov.sibelius.xs4all.nl>
On Thu, 13 Dec 2012 14:47:51 +0100, Mark Kettenis wrote:
> > I am going to do some cleanup, but how far back do we want
> > to keep?
I need only the very latest snapshot. For more I (=Fedora releases) would
need all the snapshots for the last approx. a year (for the case a Fedora
release is made from one of those).
> What's the rationale for having snapshots at all when we have anoncvs access?
As they are made from "src-release", that is like "make dist".
Users fail to build it from repository (such as due to bison + flex).
Jan
next prev parent reply other threads:[~2012-12-13 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 12:44 Joel Brobecker
2012-12-13 13:48 ` Mark Kettenis
2012-12-13 13:52 ` Joel Brobecker
2012-12-13 13:54 ` Jan Kratochvil [this message]
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=20121213135429.GA13441@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.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