From: Michael Hudson-Doyle via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Michael Hudson-Doyle via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] Use support_open_dev_null_range io/tst-closefrom, misc/tst-close_range, and posix/tst-spawn5 (BZ #28260)
Date: Tue, 21 Sep 2021 22:30:13 +1200 [thread overview]
Message-ID: <CAJ8wqtcYfNe5dr4Z-CMhVPzgqpW8Bcmfbh-8aRSN1SfnErmakA@mail.gmail.com> (raw)
In-Reply-To: <CAJ8wqtdMFv3WreEvm8QO8W=UzkTDRJnA6b1aj63D+5QaJD_jzg@mail.gmail.com>
On Tue, 21 Sept 2021 at 11:20, Michael Hudson-Doyle <
michael.hudson@canonical.com> wrote:
> On Mon, 20 Sept 2021 at 22:55, Florian Weimer <fweimer@redhat.com> wrote:
>
>> * Michael Hudson-Doyle:
>>
>> > I found this guide:
>> >
>> https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
>> > which perhaps is a little out of date wrt copyright assignments?
>> > (Although I'm 99.99% certain Canonical has a copyright assignment on
>> > file with the FSF anyway). I've created a patchwork account (mwhudson)
>> > and a wiki account (MichaelHudsonDoyle), I think the next step would
>> > be to fill out this form?
>> > https://sourceware.org/cgi-bin/pdw/ps_form.cgi
>>
>> Yes, that's the right form to fill out. You can list me as the
>> approver.
>>
>
> Done, thanks.
>
>
>> In the meantime, it might make sense to check internally if your
>> contributions will be covered by Canonical assignment, so that you know
>> whether posted patches should have Signed-off-by: or not.
>>
>
> I've asked about this, hopefully will find out soon. I guess it's not
> needed to cherry-pick something to 2.34/master!
>
OK, I've pushed these commits to release/2.34/master and emailed
libc-stable. Thanks for the support!
I'm not super familiar with email-based git development so apologies in
advance for any mis-steps...
Cheers,
mwh
prev parent reply other threads:[~2021-09-21 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 19:28 [PATCH 0/2] Fix close_range/closefrom tests Adhemerval Zanella via Libc-alpha
2021-08-24 19:28 ` [PATCH 1/2] support: Add support_open_dev_null_range Adhemerval Zanella via Libc-alpha
2021-08-24 19:28 ` [PATCH 2/2] Use support_open_dev_null_range io/tst-closefrom, misc/tst-close_range, and posix/tst-spawn5 (BZ #28260) Adhemerval Zanella via Libc-alpha
2021-08-25 3:15 ` Michael Hudson-Doyle via Libc-alpha
2021-08-25 3:41 ` Michael Hudson-Doyle via Libc-alpha
2021-08-25 8:40 ` Michael Hudson-Doyle via Libc-alpha
2021-08-25 11:46 ` Adhemerval Zanella via Libc-alpha
2021-09-14 0:46 ` Michael Hudson-Doyle via Libc-alpha
2021-09-16 12:09 ` Florian Weimer via Libc-alpha
2021-09-16 23:44 ` Michael Hudson-Doyle via Libc-alpha
2021-09-17 10:12 ` Florian Weimer via Libc-alpha
2021-09-19 21:57 ` Michael Hudson-Doyle via Libc-alpha
2021-09-20 10:54 ` Florian Weimer via Libc-alpha
2021-09-20 23:20 ` Michael Hudson-Doyle via Libc-alpha
2021-09-21 10:30 ` Michael Hudson-Doyle via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ8wqtcYfNe5dr4Z-CMhVPzgqpW8Bcmfbh-8aRSN1SfnErmakA@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=michael.hudson@canonical.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).