From: Mike Frysinger <vapier@gentoo.org>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: cgen@sourceware.org
Subject: Re: [PATCH] start a simple MAINTAINERS file
Date: Tue, 14 Sep 2021 16:45:39 -0400 [thread overview]
Message-ID: <YUEJ829oV5V6WlVo@vapier> (raw)
In-Reply-To: <87tuimzzl9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On 14 Sep 2021 22:12, Jose E. Marchesi wrote:
> > ---
> > MAINTAINERS | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> > create mode 100644 MAINTAINERS
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > new file mode 100644
> > index 000000000000..190d00577bab
> > --- /dev/null
> > +++ b/MAINTAINERS
> > @@ -0,0 +1,23 @@
> > + CGEN Maintainers
> > +
> > +This file describes different groups of people who are, together, the
> > +maintainers and developers of the CGEN project. Don't worry - it sounds
> > +more complicated than it really is.
> > +
> > +If you are considering contributing a patch, you'll want to send them to
> > +cgen@sourceware.org. See the mailing list page for more information:
> > +https://sourceware.org/mailman/listinfo/cgen
> > +
> > + Global Maintainers
> > +
> > +Jose E. Marchesi jose.marchesi@oracle.com
>
> Now wait a minute... how did that happen? :D
>
> I actually sent an email to Frank today, offering my help with the
> maintenance, but he hasn't come back to me yet. Right now I don't have
> the right to actually approve patches.
tbh, i just looked at recent commit history. i have no idea who is in
charge :).
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-14 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 19:45 Mike Frysinger
2021-09-14 20:12 ` Jose E. Marchesi
2021-09-14 20:15 ` Frank Ch. Eigler
2021-09-14 21:04 ` Jose E. Marchesi
2021-09-14 20:45 ` Mike Frysinger [this message]
2021-09-14 20:47 ` [PATCH v2] " Mike Frysinger
2021-09-14 21:14 ` Jose E. Marchesi
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=YUEJ829oV5V6WlVo@vapier \
--to=vapier@gentoo.org \
--cc=cgen@sourceware.org \
--cc=jemarch@gnu.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).