This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS, 2015 edition
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Stan Shebs <stanshebs at google dot com>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Mon, 25 May 2015 02:17:52 +0200
- Subject: Re: TLS, 2015 edition
- Authentication-results: sourceware.org; auth=none
- References: <CA+5-Q5K7M3oJ-vvRP24GiCEHqnohWgqPkc7_6K9CLzc6a_MTcA at mail dot gmail dot com> <551A763A dot 5070909 at arm dot com> <CA+5-Q5K3fmH0AM=qa6uCT0zPvF+XLLopzpk0MzWCSK5Bzn9CNw at mail dot gmail dot com> <551AC46C dot 8060901 at arm dot com> <CA+5-Q5JNL+eeyJt_jb0iB_T393NJvWTZc6t3k1vLKHu4zA6TSA at mail dot gmail dot com> <20150406202045 dot GP16816 at vapier> <CA+5-Q5KDW=MdVjA0o=Cza+Wqay8ENFXmWVbfwmN5rAfqRv6_YA at mail dot gmail dot com> <20150406212835 dot GQ16816 at vapier>
On Mon, Apr 06, 2015 at 05:28:35PM -0400, Mike Frysinger wrote:
> On 06 Apr 2015 15:47, Stan Shebs wrote:
> > On Mon, Apr 6, 2015 at 3:20 PM, Mike Frysinger wrote:
> > > On 31 Mar 2015 11:33, Stan Shebs wrote:
> > > > The Google-local patch is a descendant of that code. (In theory Google
> > > > ought to have a git branch, but I only see ones for Roland?)
> > >
> > > if the Google maintainers of an internal glibc patchset (i'm assuming you're
> > > referring to the glibc in the GRTE) wanted to use the public glibc git for
> > > their work, i don't think we'd have a problem with that. it'd most likely be
> > > more of an issue getting those people push access (assuming they don't already
> > > have it). unfortunately, the server is running plain git which doesn't do
> > > per-branch ACLs like Gerrit supports.
> >
> > I don't know that ACLs are critical - the obstacles to a public git
> > branch are mostly inertia, and the need for some import script
> > tinkering.
>
> i mean it might be easier giving out access to known vendors (like Google) if we
> could constrain them to the vendor branch namespace. otherwise, since you get
> full access to the git repo, we don't give out access freely.
> -mike
Main obstacle is still inertia. We could find somebody from google to
trust doing periodic sync of google branch. It would be same as syncing
fedora/gentoo ones.