From: Phil Edwards <phil@jaj.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: DJ Delorie <dj@delorie.com>,
gcc-patches@gcc.gnu.org, neroden@twcny.rr.com,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
Nick Clifton <nickc@redhat.com>
Subject: Re: (toplevel patch) Remove 'vault' targets
Date: Thu, 28 Nov 2002 12:14:00 -0000 [thread overview]
Message-ID: <20021128151416.A23023@disaster.jaj.com> (raw)
In-Reply-To: <3DE65CE4.5020908@redhat.com>; from ac131313@redhat.com on Thu, Nov 28, 2002 at 01:13:56PM -0500
On Thu, Nov 28, 2002 at 01:13:56PM -0500, Andrew Cagney wrote:
> > We could start committing to src if we don't mind src and gcc being
> > out of sync until gcc's freeze is over.
>
> M'kay by me. Nick? Preference?
>
> Andrew
>
> (I keep reading that as ``until gcc freezes over'' ... :-)
We should change the homepage scheme based on the state of the branches.
Normal development uses a normal color/layout scheme. When a branch is
frozen, all the colors are shades of blue, and icicles hang from the images.
That way people could tell at a glance the state of development.
Heck NO I'm not volunteering to implement it. :-)
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next prev parent reply other threads:[~2002-11-28 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 18:46 Nathanael Nerode
2002-11-27 20:29 ` Andrew Cagney
2002-11-27 21:01 ` DJ Delorie
2002-11-28 10:14 ` Andrew Cagney
2002-11-28 12:14 ` Phil Edwards [this message]
2002-11-29 0:54 ` Nick Clifton
2002-11-29 7:22 ` Andrew Cagney
2002-11-29 7:52 ` DJ Delorie
2002-11-29 8:18 ` Nick Clifton
2002-11-29 8:20 ` DJ Delorie
2002-11-29 9:00 ` Nick Clifton
2002-11-29 9:19 ` Andrew Cagney
2002-11-29 9:48 ` DJ Delorie
2002-12-02 12:23 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 23:25 Nathanael Nerode
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=20021128151416.A23023@disaster.jaj.com \
--to=phil@jaj.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=nickc@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