From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: New branch created for "available features" support
Date: Fri, 03 Mar 2006 21:55:00 -0000 [thread overview]
Message-ID: <upsl32nxk.fsf@gnu.org> (raw)
In-Reply-To: <20060303213507.GA20474@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 3 Mar 2006 16:35:07 -0500)
> Date: Fri, 3 Mar 2006 16:35:07 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> Feel free to ignore this; it's mostly a brain dump.
A good place to keep this stuff and maintain it as ideas evolve and
design decisions are made is in gdbint.texinfo on that branch. That
way, when this becomes part of the mainstream, it is automagically
documented ;-)
Thanks.
next prev parent reply other threads:[~2006-03-03 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 21:35 Daniel Jacobowitz
2006-03-03 21:55 ` Eli Zaretskii [this message]
2006-03-03 21:58 ` Daniel Jacobowitz
2006-03-04 9:09 ` Eli Zaretskii
2006-03-03 22:36 ` Jim Blandy
2006-03-04 14:34 ` Daniel Jacobowitz
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=upsl32nxk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).