From: Carlos O'Donell <carlos@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>,
GNU C Library <libc-alpha@sourceware.org>
Cc: nd@arm.com
Subject: Re: Vendor branch namespace request
Date: Thu, 31 Aug 2017 16:13:00 -0000 [thread overview]
Message-ID: <ffb7eab1-b936-f08f-7622-848f78755e9c@redhat.com> (raw)
In-Reply-To: <59A6DC6D.5040905@arm.com>
On 08/30/2017 10:40 AM, Szabolcs Nagy wrote:
> On 23/08/17 11:47, Szabolcs Nagy wrote:
>> Based on https://sourceware.org/glibc/wiki/GlibcGit
>> I'd like to request an arm/* branch namespace to create an arm/ilp32
>> branch as discussed earlier.
>>
>> Owners:
>> glibc maintainers working at arm.
>> mshawcroft, nsz.
>>
>> Committers:
>> the owners can commit.
>> others can commit after approval by the owners on libc-alpha.
>>
>
> ping.
>
According to the rules "if nobody calls you rude names, then consider it approved"
Approved :-)
Please update https://sourceware.org/glibc/wiki/GlibcGit#Name_Space_Table.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2017-08-31 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 10:47 Szabolcs Nagy
2017-08-30 15:40 ` Szabolcs Nagy
2017-08-31 16:13 ` Carlos O'Donell [this message]
2017-09-01 13:39 ` Szabolcs Nagy
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=ffb7eab1-b936-f08f-7622-848f78755e9c@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=szabolcs.nagy@arm.com \
/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).