From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gdb@sources.redhat.com
Subject: Re: PATCH: autoconfiscate SPU
Date: Sun, 03 Feb 2002 12:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0202031128180.8089-100000@nerodeguest> (raw)
In-Reply-To: <20020129103703.A6618@nevyn.them.org>
Ok, I've submitted a working autoconfiscation of SPU to the gdb-patches
list. I now need
1. The copyright assignment forms to fill out
2. this patch to be reviewed and hopefully committed
Can someone help me here?
--Nathanael Nerode
neroden@doctor.moo.mud.org
neroden@twcny.rr.com
parent reply other threads:[~2002-02-03 16:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20020129103703.A6618@nevyn.them.org>]
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.21.0202031128180.8089-100000@nerodeguest \
--to=neroden@doctormoo.dyndns.org \
--cc=gdb@sources.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