From: Richard Guenther <rguenther@suse.de>
To: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>
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, 20 Sep 2009 19:50:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.0909202148510.4520@zhemvz.fhfr.qr> (raw)
In-Reply-To: <4AB6851C.2070005@sophia.inria.fr>
On Sun, 20 Sep 2009, Theodore Papadopoulo wrote:
> 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.
> >
> > <h3>Schedule</h3>
> > -<p>Development on our main branch will proceed in three stages. Each
> > -stage will be two months in length.</p>
> > +<p>Development on our main branch will proceed in three stages.</p>
> Just a minor tweak...
> Since there are only effectively two stages, wouldn't it be better to state
> two stages here ?
Effectively after leaving Stage 3 we enter a "Stage 4" before the
release branch is created. So all, two, three and four would be
in some way correct ;) Thus I didn't bother to change this detail.
Richard.
next prev parent reply other threads:[~2009-09-20 19:50 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 [this message]
2009-09-27 6:23 ` Gerald Pfeifer
2009-09-27 19:17 ` Richard Guenther
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.0909202148510.4520@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--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).