This is the mail archive of the
mailing list for the glibc project.
Re: Request for google/ namespace
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Stan Shebs <stanshebs at google dot com>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Wed, 26 Aug 2015 16:59:10 -0700 (PDT)
- Subject: Re: Request for google/ namespace
- Authentication-results: sourceware.org; auth=none
- References: <CA+5-Q5JdywjjOsUpwXcznZ7siA41Fp_r28MEST8EoO7g04roeg at mail dot gmail dot com>
> As many on this list already know, Google has long maintained an
> internal version of glibc, under the name GRTE, that is the main C
> library for binaries running on production servers. There have been
> sporadic releases of the sources in the past, for instance at
> https://code.google.com/p/google-search-appliance-mirror/ , but we
> would like to use git to set up a higher-bandwidth conduit for
> changes, as the set of local patches is now non-trivial and should be
> more visible.
I applaud this effort!
> So to start with, it seems useful to define a namespace:
Approved to have one, but I think vapier and I should be on the owners list
I'd quibble a bit with the layout underneath google/, but it's only we
Google folks who need to agree about that (and we can discuss that either
here or internally). Just in anticipation of unrelated Google branches
that might come along in the future, I'd suggest that you use google/grte/*
for the layout you've described.
Now you just need to proceed with updating
and the other steps listed there. Step 3 is already done, since I
just had you added to the group and everybody else was already there.
You can't edit the wiki yet because you don't have an account.
Get one here:
Then I can add you to EditorGroup so you can actually edit the wiki,
which is what steps 2, 4, and 5 require.