public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Gerald Pfeifer" <gerald@pfeifer.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.1 snapshots
Date: Tue, 27 May 2008 21:49:00 -0000	[thread overview]
Message-ID: <84fc9c000805271449v61f4c371l16c3ffec20fb4188@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.10.0805272149370.6827@acrux.dbai.tuwien.ac.at>

On Tue, May 27, 2008 at 10:48 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> At this point, we have three open release branches (4.1, 4.2, and 4.3)
> and trunk.  Currently we are generating weekly snapshots for all four
> of these.
>
> A while ago we agreed, for a number of reasons, not to do any further
> GCC 4.1.x releases and the speed of changes on that branch has noticably
> slowed down.
>
> My recommendation in my very unoffical role as "carer of the snapshots"
> is to stop doing those weekly snapshots for the 4.1 branch, and I will
> be happy to roll a new snapshot upon request in case someone (like a
> GNU/Linux or BSD distribution would like to see one for their packages)
> in that case.
>
> If there is agreement, I am happy to take the appropriate technical
> steps.
>
> Thoughts?

I'd rather close the 4.2 branch than the 4.1 one.  Unfortunately the FSF
has put us in a situation where we can't do any more 4.1 releases.  Can we
slow down the 4.1 snapshot interval to 4 weeks instead?

Thanks,
Richard.

  reply	other threads:[~2008-05-27 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 20:48 Gerald Pfeifer
2008-05-27 21:49 ` Richard Guenther [this message]
2008-05-27 22:23   ` Joe Buck
2008-05-28  1:11     ` NightStrike
2008-05-28 17:13       ` Joe Buck
2008-05-28 18:15         ` Richard Guenther
2008-05-28 18:31           ` Joe Buck
2008-05-29 23:48             ` Joseph S. Myers
2008-05-30  0:11               ` Joe Buck
2008-05-28 16:33 ` Mark Mitchell

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=84fc9c000805271449v61f4c371l16c3ffec20fb4188@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.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).