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: Mon, 20 Sep 2021 09:57:03 +1200 [thread overview]
Message-ID: <CAJ8wqteyUZ4CE=L-xHe=8wqNr0v3-_ZDiwnP6cVan+RFx3ORAA@mail.gmail.com> (raw)
In-Reply-To: <8735q3fr4b.fsf@oldenburg.str.redhat.com>
On Fri, 17 Sept 2021 at 22:12, Florian Weimer <fweimer@redhat.com> wrote:
> * Michael Hudson-Doyle:
>
> > What does taking care of it mean in this context? I can't commit it,
> > but I can confirm that the patches cherry-pick cleanly to
> > release/2.34/master. Is it expected to file a bug in bugzilla for a
> > backport request?
>
> I think you could apply for commit rights so that you can do the
> backport yourself (basically, “git cherry-pick -x” it, test it, then
> push to sourceware).
>
OK, sure!
> What do you think?
>
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
Cheers,
mwh
next prev parent reply other threads:[~2021-09-19 21:57 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 [this message]
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
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='CAJ8wqteyUZ4CE=L-xHe=8wqNr0v3-_ZDiwnP6cVan+RFx3ORAA@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).