From: Florian Weimer <fweimer@redhat.com>
To: Daurnimator <quae@daurnimator.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3][BZ 21340] add support for POSIX_SPAWN_SETSID
Date: Thu, 06 Apr 2017 12:37:00 -0000 [thread overview]
Message-ID: <75eb12d0-a3f1-2b37-90d5-0a9a3f7f9a99@redhat.com> (raw)
In-Reply-To: <CAEnbY+dyj535NeaOz6EbVU6od3JKV+61PTWx7EXbXeZHCa5G6g@mail.gmail.com>
On 04/05/2017 01:01 PM, Daurnimator wrote:
>> You aren't listed in MAINTAINERS on the wiki. Do you have a GNU copyright
>> assignment on file?
>
> I do not.
Would you be willing to assign copyright for this and future changes?
If yes, please pick request-assign.future from here:
<https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment>
and send the filled-out form to <assign@gnu.org>. As far as I
understand it, citizens from most countries can complete the process
electronically these days.
Thanks,
Florian
next prev parent reply other threads:[~2017-04-06 12:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 5:41 daurnimator
2017-04-05 8:34 ` Florian Weimer
2017-04-05 11:01 ` Daurnimator
2017-04-06 12:37 ` Florian Weimer [this message]
2017-04-06 13:22 ` Zack Weinberg
2017-04-06 13:23 ` Florian Weimer
2017-04-06 13:24 ` Zack Weinberg
2017-04-07 12:27 ` Daurnimator
2017-04-07 13:46 ` Zack Weinberg
2017-04-09 13:22 ` Daurnimator
2017-04-21 5:04 ` Daurnimator
2017-04-21 12:39 ` Adhemerval Zanella
2017-04-21 14:13 ` Adhemerval Zanella
2017-04-21 14:24 ` Florian Weimer
2017-04-21 18:29 ` Adhemerval Zanella
2017-04-21 19:53 ` Joseph Myers
2017-04-21 20:43 ` Adhemerval Zanella
2017-04-21 20:04 ` Florian Weimer
2017-04-21 20:43 ` Adhemerval Zanella
2017-04-21 20:47 ` Florian Weimer
2017-04-21 18:24 ` Joseph Myers
2017-04-21 18:26 ` Adhemerval Zanella
2017-04-05 12:31 ` Joseph Myers
2017-04-05 12:44 ` Joseph Myers
2017-04-05 12:58 ` Szabolcs Nagy
2017-04-05 15:02 ` Joseph Myers
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=75eb12d0-a3f1-2b37-90d5-0a9a3f7f9a99@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=quae@daurnimator.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).