From: Cary Coutant <ccoutant@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Binutils <binutils@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Experimental branches
Date: Tue, 23 Dec 2014 17:38:00 -0000 [thread overview]
Message-ID: <CAHACq4qPSC6YX_uAcT0n35QD61LxATcKhjG0BXQ-qRhQ+GU63A@mail.gmail.com> (raw)
In-Reply-To: <20141223132714.GA11973@adacore.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
next prev parent reply other threads:[~2014-12-23 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHACq4rzgyE-2cM=UV30-1MWKHsWqwF1QdtuAujgYzFJ=8Y08A@mail.gmail.com>
2014-12-23 13:27 ` Joel Brobecker
2014-12-23 17:38 ` Cary Coutant [this message]
2014-12-23 17:42 ` H.J. Lu
2014-12-23 18:08 ` Joel Brobecker
2014-12-23 18:21 ` Cary Coutant
2014-12-23 18:26 ` H.J. Lu
2014-12-24 0:20 ` Joel Brobecker
2015-01-15 21:56 ` Cary Coutant
2015-01-15 22:48 ` H.J. Lu
2015-01-15 23:04 ` Cary Coutant
2015-01-15 23:20 ` H.J. Lu
2015-01-16 18:41 ` Richard Henderson
2015-01-16 19:07 ` Cary Coutant
2015-01-16 19:26 ` Doug Evans
2015-01-16 3:14 ` Joel Brobecker
2015-01-15 23:57 ` Alan Modra
2015-01-16 3:19 ` Joel Brobecker
2015-01-16 18:42 ` Richard Henderson
2015-01-17 4:17 ` Joel Brobecker
2015-01-17 3:24 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHACq4qPSC6YX_uAcT0n35QD61LxATcKhjG0BXQ-qRhQ+GU63A@mail.gmail.com \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).