Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Yue Lu <hacklu.newborn@gmail.com>,
	Joel Brobecker <brobecker@adacore.com>
Cc: <bug-hurd@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [patch] for mig check in GDB's configure
Date: Fri, 17 May 2013 07:00:00 -0000	[thread overview]
Message-ID: <87k3myks5p.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20130517053042.GD4017@adacore.com>


[-- Attachment #1.1: Type: text/plain, Size: 1524 bytes --]

Hi!

On Fri, 17 May 2013 09:30:42 +0400, Joel Brobecker <brobecker@adacore.com> wrote:
> > After reviewing and testing it, I now checked in your patch (very minor
> > coding style and wording changes).  Congratulations to your first
> > contribution!  :-)
> > 
> > 2013-05-16  Yue Lu  <hacklu.newborn@gmail.com>
> > 
> > 	* configure.ac: Ensure MIG is available when building for GNU Hurd
> > 	hosts.
> > 	* configure: Regenerate.
> 
> I cannot remember if we said Yue had a copyright assignment on file,
> or not. I checked the file, and couldn't locate him. Can you clarify?

No, we have not yet started that process -- but indeed perhaps already
should.  Yue, the GDB project, as part of the GNU project, requires
copyright assignment for any substantial changes,
<http://www.gnu.org/licenses/why-assign.html>.  For simplicity, I suggest
you use the »assignment form for your past and future changes«, which I
have attached to this email.  Would that be OK for you?  As you're
working on Hurd-related things, I suggest you request papers for all
relevant projects, so please specify the following: GDB, Hurd, GNU Mach,
glibc.  When you send the email, please put me in CC.

> This patch is small enough that it can be accepted without regardless;
> but if we do, I'd like to mark it as such in the ChangeLog entry
> (using "(tiny change)", as mentioned by the guide for GNU maintainers).

Sorry, I have not been aware of actually having to do this.  Now added.


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 --]

  parent reply	other threads:[~2013-05-17  7:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB8fV=gfGtguD28FGa-A5DZT8jqvEA1AoaK4dO=cHMQcCVvB-w@mail.gmail.com>
2013-05-03  8:28 ` Thomas Schwinge
2013-05-03 10:44   ` 陆岳
     [not found]     ` <87txmkxlu6.fsf@violet.siamics.net>
2013-05-04  8:29       ` Yue Lu
2013-05-16 21:55         ` Thomas Schwinge
2013-05-17  5:30           ` Joel Brobecker
2013-05-17  6:34             ` Yue Lu
2013-05-17  7:00             ` Thomas Schwinge [this message]
2013-05-17  7:07               ` Joel Brobecker
2013-05-04 17:22     ` Doug Evans
2013-05-05  5:31       ` Yue Lu
2013-05-05 17:35         ` Doug Evans
2013-05-16 22:10           ` Thomas Schwinge
2013-05-03 14:51   ` Pedro Alves

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=87k3myks5p.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hacklu.newborn@gmail.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