public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: Maintainer status: patch review required?
Date: Tue, 29 Jun 2021 12:29:40 +0200	[thread overview]
Message-ID: <87a6n9m0a3.fsf@oldenburg.str.redhat.com> (raw)

<https://sourceware.org/glibc/wiki/MAINTAINERS> says this:

| Where someone is listed in the Maintainers column, they may at their
| discretion consider their own patches in that area to have consensus
| without waiting for third-party review, although other people may
| still review patches in that area and it may turn out that a patch by
| someone listed does not in fact have consensus and needs changing or
| reverting.

But I'm not sure to what extent we follow that process today.

I have some libresolv changes coming up (rather tedious stuff—splitting
things into files, GNU style conversion, then moving into libc), and I'm
listed as the network maintainer.  So per the wiki, I could just push
them.  Is this what we want?

Thanks,
Florian


             reply	other threads:[~2021-06-29 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 10:29 Florian Weimer [this message]
2021-06-29 12:46 ` Siddhesh Poyarekar

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=87a6n9m0a3.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).