From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Michael Snyder <msnyder@specifix.com>,
jonatan perry <jonatan44@gmail.com>,
gdb@sourceware.org
Subject: Re: Record patch in main GDB tree?
Date: Tue, 08 Apr 2008 10:58:00 -0000 [thread overview]
Message-ID: <20080407192958.GB27919@ednor.casa.cgf.cx> (raw)
In-Reply-To: <1207595611.31772.332.camel@localhost.localdomain>
On Mon, Apr 07, 2008 at 12:13:31PM -0700, Michael Snyder wrote:
>On Mon, 2008-04-07 at 20:32 +0200, jonatan perry wrote:
>> Hi list :)
>> I was wonder - why does the *record patch isn't merged to the main GDB
>> development tree?
>>
>> *http://sourceforge.net/projects/record/
>>
>> Thanks,
>> Jonatan Perry.
>
>First I recall hearing of it.
>
>Has anybody offered to submit it to gdb?
Does it actually work?
cgf
next prev parent reply other threads:[~2008-04-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d592e5da0804071129j2819b2fej3e65361088a19be6@mail.gmail.com>
2008-04-07 19:06 ` jonatan perry
2008-04-07 19:30 ` Michael Snyder
2008-04-08 10:58 ` Christopher Faylor [this message]
2008-04-08 18:58 ` jonatan perry
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=20080407192958.GB27919@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jonatan44@gmail.com \
--cc=msnyder@specifix.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