From: Zack Weinberg <zack@codesourcery.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Richard Henderson <rth@redhat.com>, Jim Blandy <jimb@redhat.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
Date: Tue, 26 Mar 2002 15:31:00 -0000 [thread overview]
Message-ID: <20020326233102.GO23331@codesourcery.com> (raw)
In-Reply-To: <20020326231730.GA1283@daikokuya.demon.co.uk>
On Tue, Mar 26, 2002 at 11:17:30PM +0000, Neil Booth wrote:
> Richard Henderson wrote:-
> > I think this is a mistake. It is completely unreasonable to have
> > the entire "major structural changes" time period concurrent with
> > "please work on making a release happen".
>
> I agree. I think the releases should be an 8-month cycle rather
> than a 6-month cycle. In other words, 4 months for destabilizing
> changes.
m3 t00.
I'll add that this is an argument for a better version control system;
most of the changes on the queue inside my head, I would have done on
a branch if CVS didn't make branches such a pain. (E.g. it takes
about 10x longer to do "cvs update" on the 3.0 branch than the trunk.)
zw
next prev parent reply other threads:[~2002-03-26 23:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 15:40 sharing libcpp between GDB and GCC Jim Blandy
2002-03-25 20:07 ` Zack Weinberg
2002-03-25 23:18 ` Neil Booth
2002-03-26 14:29 ` gcc development schedule [Re: sharing libcpp between GDB and GCC] Richard Henderson
2002-03-26 14:37 ` David Edelsohn
2002-03-26 21:32 ` Andreas Jaeger
2002-03-26 15:17 ` Neil Booth
2002-03-26 15:30 ` Tom Lord
2002-03-26 15:40 ` David Edelsohn
2002-03-26 16:03 ` Tom Lord
2002-03-26 16:41 ` Tim Hollebeek
2002-03-26 22:23 ` Eli Zaretskii
2002-03-26 22:43 ` Tom Lord
2002-03-27 7:18 ` mike stump
2002-03-27 9:00 ` law
2002-03-27 10:13 ` Neil Booth
2002-03-26 22:45 ` Tom Lord
2002-03-26 23:11 ` Daniel Berlin
2002-03-26 23:53 ` Tom Lord
2002-03-27 4:32 ` Fergus Henderson
2002-03-27 6:30 ` Andrew Cagney
2002-03-27 6:43 ` Gianni Mariani
2002-03-26 22:39 ` Andreas Jaeger
2002-03-26 22:54 ` Tom Lord
2002-03-26 15:31 ` Zack Weinberg [this message]
2002-03-27 6:01 Robert Dewar
2002-03-27 19:17 Kaveh R. Ghazi
2002-03-27 19:46 ` Zack Weinberg
2002-03-28 1:24 ` Gerald Pfeifer
2002-03-28 1:53 ` Jason Molenda
2002-03-28 2:01 ` Jason Molenda
2002-03-28 7:17 ` Christopher Faylor
2002-03-28 9:01 ` David O'Brien
2002-03-28 21:29 ` Christopher Faylor
2002-03-28 9:00 ` David O'Brien
2002-04-03 14:19 ` Jim Blandy
2002-04-03 14:29 ` Phil Edwards
2002-03-28 12:34 ` Phil Edwards
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=20020326233102.GO23331@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=neil@daikokuya.demon.co.uk \
--cc=rth@redhat.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