From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: start a MAINTAINERS file
Date: Wed, 24 Jan 2024 15:43:21 +0100 [thread overview]
Message-ID: <ZbEiCalTOAIpSTCZ@calimero.vinschen.de> (raw)
In-Reply-To: <ZbEWqwNhjGUfzaVC@vapier>
On Jan 24 08:54, Mike Frysinger wrote:
> On 24 Jan 2024 12:17, Corinna Vinschen wrote:
> > On Jan 23 23:33, Mike Frysinger wrote:
> > > --- /dev/null
> > > +++ b/libgloss/MAINTAINERS
> > > @@ -0,0 +1,13 @@
> > > + libgloss Maintainers
> > > +
> > > +libgloss is part of Newlib project, so see the file newlib/MAINTAINERS
> > > +for more people. This file is intended to find libgloss-specific people
> > > +where it makes sense.
> > > +
> > > +
> > > + Blanket Write Privileges
> > > +
> > > +The official maintainers of libgloss:
> > > +
> > > +Jeff Johnston jjohnstn@redhat.com
> > > +Mike Frysinger vapier@gentoo.org
> >
> > Great, sure! You can also add me as backup.
>
> i was trying to say that newlib/MAINTAINERS functions as the fallback so we
> didn't have to duplicate all the sections. should i rephrase the intro text
> to be more clear ?
No, it's ok. I just missed to pay attention to the comment *blush*...
> i didn't put you here because, from the other thread, it sounded like you
> didn't generally pay attention to libgloss changes.
I do, I just don't feel qualified, so I usually wait for an ACK
from a reviewer.
Anyway, just push as is.
Thanks,
Corinna
prev parent reply other threads:[~2024-01-24 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 4:33 Mike Frysinger
2024-01-24 11:17 ` Corinna Vinschen
2024-01-24 13:54 ` Mike Frysinger
2024-01-24 14:43 ` Corinna Vinschen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZbEiCalTOAIpSTCZ@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).