From: Jeff Johnston <jjohnstn@redhat.com>
To: newlib@sourceware.org, Mike Frysinger <vapier@gentoo.org>,
Jeff Johnston <jjohnstn@redhat.com>,
Dimitar Dimitrov <dimitar@dinux.eu>
Subject: Re: [PATCH v3 2/2] libgloss: pru: Trim crt0-minrt.o
Date: Tue, 23 Jan 2024 10:55:54 -0500 [thread overview]
Message-ID: <CAOox84twbspM6yme5NpQJNP9HPoSUBKEtbrtx+RmVHkwXrba9A@mail.gmail.com> (raw)
In-Reply-To: <Za-BAoLkaAPwaCo6@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Tue, Jan 23, 2024 at 4:04 AM Corinna Vinschen <vinschen@redhat.com>
wrote:
> On Jan 22 12:27, Mike Frysinger wrote:
> > On 22 Jan 2024 11:04, Corinna Vinschen wrote:
> > > On Jan 20 13:57, Mike Frysinger wrote:
> > > > On 20 Jan 2024 17:15, Dimitar Dimitrov wrote:
> > > > > On Sat, Jan 20, 2024 at 08:46:36AM -0500, Mike Frysinger wrote:
> > > > > > should you be listed in newlib/MAINTAINERS for pru ?
> > > > >
> > > > > Yes, I would be honoured.
> > > > >
> > > > > I've been running and monitoring CI for the GNU toolchain for PRU,
> > > > > including newlib, for a few years. And I intend to continue doing
> so.
> > > >
> > > > send a patch for Corinna & Jeff to approve :)
> > > >
> > > > do you have push access to newlib now ? might be worth asking for
> that too
> > > > so you can be added to the "write privileges after getting approval"
> section.
> > >
> > > libgloss isn't my playfield, so I was deferring this to Jeff.
> >
> > any value in carving out a more specific libgloss/MAINTAINERS ?
> > i'd be happy to be a "global" maintainer there ... just not in newlib :).
>
> That sounds really good to me. Jeff?
>
>
I agree.
-- Jeff J.
> Corinna
>
>
next prev parent reply other threads:[~2024-01-23 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 17:19 [PATCH v3 1/2] libgloss: merge pru into top-level Makefile Dimitar Dimitrov
2024-01-04 17:19 ` [PATCH v3 2/2] libgloss: pru: Trim crt0-minrt.o Dimitar Dimitrov
2024-01-20 7:01 ` Dimitar Dimitrov
2024-01-20 13:46 ` Mike Frysinger
2024-01-20 15:15 ` Dimitar Dimitrov
2024-01-20 18:57 ` Mike Frysinger
2024-01-22 10:04 ` Corinna Vinschen
2024-01-22 17:27 ` Mike Frysinger
2024-01-23 9:04 ` Corinna Vinschen
2024-01-23 15:55 ` Jeff Johnston [this message]
2024-01-22 18:57 ` Jeff Johnston
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=CAOox84twbspM6yme5NpQJNP9HPoSUBKEtbrtx+RmVHkwXrba9A@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=dimitar@dinux.eu \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).