This is the mail archive of the
mailing list for the binutils project.
Re: Experimental branches
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Cary Coutant <ccoutant at google dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, Binutils <binutils at sourceware dot org>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 23 Dec 2014 09:42:03 -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> <CAHACq4qPSC6YX_uAcT0n35QD61LxATcKhjG0BXQ-qRhQ+GU63A at mail dot gmail dot com>
On Tue, Dec 23, 2014 at 9:38 AM, Cary Coutant <firstname.lastname@example.org> wrote:
>> 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
>> 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
I like "user" or "users".
> 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?
We can rename a branch with:
# git branch -m hjl/pr17729 user/hjl/pr17729
# git push origin :hjl/pr17729
# git push -u origin user/hjl/pr17729