From: Daniel Berlin <dan@cgsoftware.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [RFC] Better apropos patch
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10003221256250.20082-200000@propylaea.anduin.com> (raw)
Message-ID: <20000401000000.EoJdkFwNIAXu5ctgjY0MatAF96vW9-r9BTIGAWEYvyY@z> (raw)
Won't double print, works *much* faster, properly displays prefixes.
Let me know what you guys think.
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-22 12:58 Daniel Berlin [this message]
2000-03-22 13:07 ` Fernando Nasser
2000-04-01 0:00 ` Daniel Berlin
[not found] <Pine.LNX.4.10.10003221307320.20082-100000@propylaea.anduin.com>
[not found] ` <38D9429B.798F82E2@redhat.com>
2000-03-22 14:43 ` Daniel Berlin+list.gdb-patches
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=Pine.LNX.4.10.10003221256250.20082-200000@propylaea.anduin.com \
--to=dan@cgsoftware.com \
--cc=gdb-patches@sourceware.cygnus.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