From: Michael Snyder <msnyder@vmware.com>
To: "tromey@redhat.com" <tromey@redhat.com>
Cc: teawater <teawater@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Fwd: broken links on gdb song page
Date: Mon, 08 Feb 2010 18:29:00 -0000 [thread overview]
Message-ID: <4B7057EB.2060908@vmware.com> (raw)
In-Reply-To: <m3r5ov8zre.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>
>>> http://cafe.colorado.edu/~tromey/other.html
> -> maybe Tom can help ...
>
> That machine was stolen from the lab a few years back, and AFAIK I don't
> have copies of any of that stuff any more. I don't even remember what
> it was a link to... the old UPS debugger song? Anyway I suggest
> removing the link.
No, it was gdb-specific "g is for ..."
This is a tragedy! Somewhere there is a recording of RMS
singing that song!
next prev parent reply other threads:[~2010-02-08 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.813.1265504414.14305.bug-gdb@gnu.org>
2010-02-08 3:16 ` teawater
2010-02-08 16:21 ` Tom Tromey
2010-02-08 16:44 ` Dave Korn
2010-02-08 18:31 ` Michael Snyder
2010-02-08 18:48 ` Michael Snyder
2010-02-08 18:29 ` Michael Snyder [this message]
2010-02-10 11:22 ` Joel Brobecker
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=4B7057EB.2060908@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.com \
--cc=tromey@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