This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: distro branches on sourceware
- From: "Ryan S. Arnold" <ryan dot arnold at gmail dot com>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, "Carlos O'Donell" <carlos at redhat dot com>, Allan McRae <allan at archlinux dot org>, Adam Conrad <adconrad at 0c3 dot net>, Aurelien Jarno <aurelien at aurel32 dot net>, Andreas Schwab <schwab at suse dot de>
- Date: Wed, 1 May 2013 23:12:29 -0500
- Subject: Re: distro branches on sourceware
- References: <518111EE dot 1060700 at archlinux dot org> <201305011454 dot 42108 dot vapier at gentoo dot org> <20130501210839 dot 56D332C096 at topped-with-meat dot com> <201305012348 dot 36036 dot vapier at gentoo dot org>
On Wed, May 1, 2013 at 10:48 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Wednesday 01 May 2013 17:08:39 Roland McGrath wrote:
>> > i've been debating doing this for a while ... half wrote an e-mail
>> > proposing a new Gentoo namespace a few times.
>>
>> Anyone (like you) who already has commit access and is authoritativish
>> for a downstream packager is more than welcome to establish a branch
>> namespace without anyone else's say-so. Just stick to some common sense
>> and collaboration-friendly rules and then just do it: pick a name that
>> is all lowercase, includes minimal or no punctuation (i.e. some internal
>> dashes if they make sense, and no other nonalphabetics, ASCII only), and
>> is well-recognized for your system (fedora, gentoo, archlinux, debian,
>> suse or opensuse, etc.); choose the rules for the namespace's use and
>> document them on the wiki; follow common conventions unless there's a
>> reason not to (e.g. yourprefix/master, yourprefix/2.34/master, etc.);
>> post about what you're doing.
>
> i was referring to the policy laid out here:
> http://sourceware.org/glibc/wiki/GlibcGit
>
> but i'll take this e-mail as automatic approval for a gentoo/ akin to the
> existing fedora/ and do some imports soonish
> -mike
I wrote the referenced policy at Roland's request when we first moved
to git and certain persons were worried about the abuse of namespace
branches.
I think the tacit policy we've been operating under as development has
matured and decentralized, and as now outlined by Roland, can be used
to revise the existing documentation to be more permissive.
Ryan S. Arnold