public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Binutils <binutils@sourceware.org>,
		gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Experimental branches
Date: Tue, 23 Dec 2014 17:42:00 -0000	[thread overview]
Message-ID: <CAMe9rOqGKgd2gF6FLEAO4JQuDzyQJ8DXw94eE3ckO=ZiEep+SA@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4qPSC6YX_uAcT0n35QD61LxATcKhjG0BXQ-qRhQ+GU63A@mail.gmail.com>

On Tue, Dec 23, 2014 at 9:38 AM, Cary Coutant <ccoutant@google.com> 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
>> 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.

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

-- 
H.J.

  reply	other threads:[~2014-12-23 17:42 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
2014-12-23 17:42     ` H.J. Lu [this message]
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='CAMe9rOqGKgd2gF6FLEAO4JQuDzyQJ8DXw94eE3ckO=ZiEep+SA@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=ccoutant@google.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).