public inbox for
 help / color / mirror / Atom feed
From: Ignacio Vargas <>
Subject: Re: Issues subscribing to newlib mailing list
Date: Wed, 25 Jan 2023 10:41:27 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]

Greetings overseers,

 From the email below, you can see I was having some issues subscribing 
to the newlib mailing list (sorry for possibly having brought down the 
site a few times). Those issue have been resolved though, I've been able 
to request subscription without issues already, but I've encounteredd 
other issues. I got the following message:

      Your subscription request has been received, and will soon be
    acted upon. Depending on the configuration of this mailing list,
    your subscription request may have to be first confirmed by you via
    email, or approved by the list moderator. If confirmation is
    required, you will soon get a confirmation email which contains
    further instructions.

I haven't received any confirmation email and it doesn't seem like I've 
bene actually added to the mailing list. I was wondering maybe I needed 
moderator approval. If you guys could help me properly join the newlib 
mailing list it would be much appreciated as I'd like to continue the 
discussion of my possibility of contributing over there.

Please reply at

Best regards,

Ignacio Vargas

On 1/24/23 04:57, Corinna Vinschen wrote:
>         CAUTION:       This email originated from outside of the organization. Do not click on any links or open attachments unless you recognize the sender and know the content is safe.
> On Jan 23 18:53, Ignacio Vargas wrote:
>> Greetings,
>> I've been trying to subscribe to the mailing list throughout the past few
>> hours but whenever I click the "subscribe" button the site returns me a 500
>> error code and then it seems the whole site goes down for a while. In which
>> case, I want to apologize for bringing down the site multiple times today.
>> I'm writing to the mailing list to get help with this issue because I needed
>> to join to ask some questions and I can't find an "administrator" contact
>> anywhere on the site.
> There's a mailing list <overseers AT sourceware DOT org> for that,
> please ask there.
>> In the interest of possibly saving us some time I'm also going to mention
>> what I needed to ask about. In case the answer is a simple "no" then I won't
>> have anymore to say anyways, but please don't feel obligated at all to
>> answer my query:
>>       I was considering writing a stripped-down baremetal version of
>>     argp
>>     (
>>     from glibc. I was wondering if I could write it as a contribution to
>>     newlib and, similarly to glibc's argp, write it using getopt. I
>>     mostly don't know if newlib would accept it because it's a library
>>     specific to GNU-C.
> Newlib already has a couple of GNU-specific functions implemented,
> so that's no problem.
> The only potential problem is the license.  If you write your argp
> implementation from scratch, you can use any BSD-like license you like.
> However, if you take the gloibc code as base, your code would be GPLed,
> which is not feasible for almost all targets supported by newlib.
> Corinna

       reply	other threads:[~2023-01-25 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2023-01-25 16:41   ` Ignacio Vargas [this message]
2023-01-25 20:48     ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).