Date: Sun, 24 Nov 2002 11:48:22 +0200 From: Vallo Kallaste <kalts@estpak.ee> To: Terry Lambert <tlambert2@mindspring.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.2.1 release import? Message-ID: <20021124094822.GA1024@tiiu.internal> In-Reply-To: <3DE06C7C.4AD24C44@mindspring.com> References: <120820000.1037929067@leeloo.intern.geht.de> <3DDDCD32.6D74D775@mindspring.com> <20021122064625.GA12620@troutmask.apl.washington.edu> <3DDE1711.6B9606B4@mindspring.com> <20021122152947.GA14766@troutmask.apl.washington.edu> <20021122180350.GB74344@dragon.nuxi.com> <20021123145236.GA2140@tiiu.internal> <3DE006AB.93802305@mindspring.com> <20021123235341.GA15054@tiiu.internal> <3DE06C7C.4AD24C44@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 23, 2002 at 10:06:52PM -0800, Terry Lambert
<tlambert2@mindspring.com> wrote:
> > > But who will bell the cat? I vote for Snuffles.
> >
> > Don't understand. Some inside joke or something based on US centric
> > TV? What are you trying to tell me? Remember I'm not native.
>
> 1930's/1940's cartoon character, "Snuffles, the mouse". Was in
> a lot of cartoons. Played the "Why?" game that children play,
> to the annoyance of his chosen victim, and the amusement of the
> people.
>
> One story was a script based on the Aesop's Fable about belling
> the cat. Here is a short reprise:
>
> 1) All of the mice decided that Something Needs To Be Done
> About The Cat(tm)
> 2) They had a big meeting
> 3) Finally, one mouse, who no one listened to very often,
> suggests that they put a bell around its neck, so they
> will be able to tell whic it's coming, and escape, to
> live in peace, in their mousey ways
> 4) No one wants to bell the cat; it's a perfect idea, which
> lacks for implementation, and there are no potential
> implementors to take the risk on behalf of the group
>
> In the cartoon version, at this point, the mouse who made the
> suggestion is volunteered by his "comrades" for the deadly duty
> ("Snuffles").
Heh, OK :-)
I'm also quite sure that gcc3.2.1 release will not find it's way to
5.0 and understand the technical points taken to guard this
position. That's why I put "possibility and IMHO" at the end of my
sentence. A patch will be good to have nevertheless, so we can test
things out even if it's not going to 5.0-RELEASE. So this boils down
to simple question of time, necessity and willingness to do the
patch. Let's end this thread.
--
Vallo Kallaste
kalts@estpak.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021124094822.GA1024>