From: Joe Buck <Joe.Buck@synopsys.COM>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
NightStrike <nightstrike@gmail.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
gcc@gcc.gnu.org
Subject: Re: GCC 4.1 snapshots
Date: Fri, 30 May 2008 00:11:00 -0000 [thread overview]
Message-ID: <20080530001033.GC21118@synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805292342350.23437@digraph.polyomino.org.uk>
On Wed, 28 May 2008, Joe Buck wrote:
> > Ah. Then the DATESTAMP change shouldn't happen if there is no
> > modification to the branch since the last DATESTAMP.
On Thu, May 29, 2008 at 11:48:31PM +0000, Joseph S. Myers wrote:
> The snapshots know nothing of whether there were any changes on the branch
> at all.
>
> I'd rather just close the branch (disable the update of DATESTAMP, disable
> snapshots, close bugs only open as 4.1 regressions after updating the
> milestones to indicate where they were fixed, switch other bugs marked as
> 4.1 regressions to more recent milestones and remove "4.1/" from their
> summaries) than add extra complexity for the sake of a dead branch.
I does seem like a lot of work for little gain. Suggestion withdrawn.
I did a search (summary contains all of the strings in
"4.1 regression", summary does not contain the string "4.2"), and got
103 bugs. Assuming that they are all marked correctly, these would
all close.
next prev parent reply other threads:[~2008-05-30 0:11 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
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 [this message]
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=20080530001033.GC21118@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=joseph@codesourcery.com \
--cc=nightstrike@gmail.com \
--cc=richard.guenther@gmail.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).