public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/8341: GCC Fails to play elevator muzak whilst compiling Date: Thu, 24 Oct 2002 12:46:00 -0000 [thread overview] Message-ID: <20021024194604.12287.qmail@sources.redhat.com> (raw) The following reply was made to PR other/8341; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: zack@gcc.gnu.org, The_1st_Immortal@crosswinds.net, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/8341: GCC Fails to play elevator muzak whilst compiling Date: Thu, 24 Oct 2002 15:39:33 -0400 On Thu, Oct 24, 2002 at 06:19:26PM -0000, zack@gcc.gnu.org wrote: > Synopsis: GCC Fails to play elevator muzak whilst compiling > > State-Changed-From-To: open->closed > State-Changed-By: zack > State-Changed-When: Thu Oct 24 11:19:25 2002 > State-Changed-Why: > Thank you for injecting a bit of humor into the release > process. At a stressful time like this, we can all use > a good joke or two. Agreed. Besides, playing music sounds like something that belongs on the 3.4-basic-improvements branch, not the mainline or release branch at this stage. Maybe I can work on that. 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 reply other threads:[~2002-10-24 19:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-24 12:46 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-24 11:19 zack 2002-10-24 10:56 The_1st_Immortal
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=20021024194604.12287.qmail@sources.redhat.com \ --to=phil@jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).