Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Nick Hudson <skrll@netbsd.org>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Provde a pid to filename conversion for NetBSD
Date: Sat, 16 Dec 2006 17:03:00 -0000	[thread overview]
Message-ID: <20061216170304.GA14012@nevyn.them.org> (raw)
In-Reply-To: <10247.82.92.89.47.1166267903.squirrel@webmail.xs4all.nl>

On Sat, Dec 16, 2006 at 12:18:23PM +0100, Mark Kettenis wrote:
> However, before I can do that, I need to be sure you've got an FSF
> copyright assignment for GDB in place.  Or Daniel, do you think there
> is not enough origional code here to warrant one?

I think that there is enough code to warrant assignment, but
fortunately Nick's got one in place already :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-12-16 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 13:23 Nick Hudson
2006-12-15 16:23 ` Nick Hudson
2006-12-15 16:37   ` Daniel Jacobowitz
2006-12-16  8:46     ` Nick Hudson
2006-12-16 11:18       ` Mark Kettenis
2006-12-16 17:03         ` Daniel Jacobowitz [this message]
2006-12-17 14:32           ` Mark Kettenis

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=20061216170304.GA14012@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=skrll@netbsd.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