From: Nagaraju Mekala <nagaraju.mekala87@gmail.com>
To: libc-alpha@sourceware.org
Subject: request for glibc wiki edit permissions
Date: Mon, 21 Aug 2017 07:01:00 -0000 [thread overview]
Message-ID: <CAN_j5p7NXpLhAbfBmjYXEtbYo7ZYA-Y5bPw_hRwPtWTky9ULTg@mail.gmail.com> (raw)
Hi All,
Can someone please provide the edit permissions to the
https://sourceware.org/glibc/wiki/Release/2.26 page.
I need to update the Microblaze regressions on the page.
I will continue to maintain the Microblaze port related items for Glibc.
Thanks,
Nagaraju
next reply other threads:[~2017-08-21 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 7:01 Nagaraju Mekala [this message]
2017-08-21 14:17 ` Carlos O'Donell
2017-08-22 5:02 ` Nagaraju Mekala
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=CAN_j5p7NXpLhAbfBmjYXEtbYo7ZYA-Y5bPw_hRwPtWTky9ULTg@mail.gmail.com \
--to=nagaraju.mekala87@gmail.com \
--cc=libc-alpha@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).