From: Richard Guenther <rguenther@suse.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Mark Mitchell <mark@codesourcery.com>
Subject: Re: [PATCH] Adjust develop.html to reflect recent practice
Date: Sun, 27 Sep 2009 19:17:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.0909271136070.4520@zhemvz.fhfr.qr> (raw)
In-Reply-To: <alpine.LSU.1.99.0909270020480.899@acrux.dbai.tuwien.ac.at>
On Sun, 27 Sep 2009, Gerald Pfeifer wrote:
> On Sun, 20 Sep 2009, Richard Guenther wrote:
> > As commented to my last status report develop.html does not reflect
> > reality anymore. The following tries to adjust it carefully in
> > this respect.
>
> I believe you got the math wrong in one case, when you went from
> four months that a branch will need to be maintained in the old
> model up to six months. Is it possible you ment to substract the
> two months Stage 2 used to take instead of add it?
Indeed, I mixed in the length of stage1. Four month would be
still about correct (2 month stage3 plus 2 month before we branch,
in the old model it was 2 month stage2 plus 2 month stage3).
> Since it seems hard to predicat the time between the end of Stage 3
> and branching, I suggest to just say "a few months".
>
> The patch below does that in its last hunk and makes one or the
> other editorial change.
>
> Thoughts?
Ok with me.
Thanks,
Richard.
next prev parent reply other threads:[~2009-09-27 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 12:35 Richard Guenther
2009-09-20 13:58 ` Dave Korn
2009-09-20 16:30 ` Mark Mitchell
2009-09-20 19:40 ` Theodore Papadopoulo
2009-09-20 19:50 ` Richard Guenther
2009-09-27 6:23 ` Gerald Pfeifer
2009-09-27 19:17 ` Richard Guenther [this message]
2009-10-04 18:52 ` Gerald Pfeifer
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=alpine.LNX.2.00.0909271136070.4520@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.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).