public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Ignacio Vargas <ignacio.vargas@rapidsilicon.com>
To: newlib@sourceware.org
Subject: Issues subscribing to mailing list
Date: Mon, 23 Jan 2023 18:53:10 -0600	[thread overview]
Message-ID: <8c916ff2-2394-6942-864a-d8b4b8bfb2f5@rapidsilicon.com> (raw)

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

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.


Please reply to me at: ignacio.vargas@rapidsilicon.com


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
    (https://www.gnu.org/software/libc/manual/html_node/Argp.html#index-argp-_0028program-argument-parser_0029)
    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.


Best regards,

Ignacio Vargas

             reply	other threads:[~2023-01-24  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  0:53 Ignacio Vargas [this message]
2023-01-24 10:57 ` Corinna Vinschen

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=8c916ff2-2394-6942-864a-d8b4b8bfb2f5@rapidsilicon.com \
    --to=ignacio.vargas@rapidsilicon.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).