This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Experimental branches
- From: Cary Coutant <ccoutant at google dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Binutils <binutils at sourceware dot org>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 23 Dec 2014 09:38:47 -0800
- Subject: Re: Experimental branches
- Authentication-results: sourceware.org; auth=none
- References: <CAHACq4rzgyE-2cM=UV30-1MWKHsWqwF1QdtuAujgYzFJ=8Y08A at mail dot gmail dot com> <20141223132714 dot GA11973 at adacore dot com>
> I'd like thirdparty branches to be under a certain namespace,
> so as to be able to disable a number of features for all third-party
> branches, on of them being email notifications, bugzilla, and IRC
> notifications.
>
> So, what do people think of using "topic/<username>/"?
Sounds good to me. At the risk of bikeshedding, "topic" sounds too
general to me -- how about "com" for company-sponsored branches (e.g.,
com/google/...") and "user" for individuals (e.g.,
"user/ccoutant/...")? Or "experimental"? But I'm OK with whatever you
decide.
That ship may already have sailed, though -- there are already quite a
few personal branches, some "<username>[-_]<topic>[-_]branch", some
"<username>/<topic>". Would it be easier to whitelist a few patterns
for branches that you *do* want those notifications for?
-cary