From: Thomas Schwinge <thomas@codesourcery.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>, <bug-hurd@gnu.org>,
<gdb-patches@sourceware.org>
Subject: Re: [PATCH,HURD] Fix reading core
Date: Thu, 11 Apr 2013 14:08:00 -0000 [thread overview]
Message-ID: <87a9p5h4ld.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20130410225432.GO17173@type.leflore.lan>
[-- Attachment #1.1: Type: text/plain, Size: 836 bytes --]
Hi!
On Thu, 11 Apr 2013 00:54:32 +0200, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> Thomas Schwinge, le Thu 11 Apr 2013 00:35:15 +0200, a écrit :
> > > Do you have write access to the GDB repository? If not, do you have
> > > copyright assignment papers on file? This patch is small enough that
> > > we can take it as a tiny patch, but if you think you're going to
> > > send more patches, we should probably get you started on those.
> >
> > I'd support all that; Samuel's not on file for GDB (but is for other
> > packages, such as Hurd proper).
>
> My other patch about x86 hardware watchpoint support might need it
> indeed. Which template should I use?
Going by your other assignments (and by knowing you) ;-), you'll want the
generic »past and future changes«; attached.
Grüße,
Thomas
[-- Attachment #1.2: request-assign.future --]
[-- Type: text/plain, Size: 965 bytes --]
Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
[What is the name of the program or package you're contributing to?]
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your postal address here.]
[Which files have you changed so far, and which new files have you written
so far?]
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-04-11 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 2:01 Samuel Thibault
2013-04-10 11:33 ` Joel Brobecker
2013-04-11 2:44 ` Thomas Schwinge
2013-04-11 3:55 ` Samuel Thibault
2013-04-11 14:08 ` Thomas Schwinge [this message]
2013-04-26 17:50 ` Samuel Thibault
2013-04-26 19:02 ` Joel Brobecker
2013-04-26 19:03 ` Alfred M. Szmidt
2013-04-30 12:02 ` Thomas Schwinge
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=87a9p5h4ld.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=samuel.thibault@gnu.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