All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: pull request labels : related to
Date: Tue, 08 Sep 2015 16:22:27 +0200	[thread overview]
Message-ID: <55EEEF23.10403@dachary.org> (raw)
In-Reply-To: <CAJ4mKGa8ELkQ85mzdQjqhriuGhxjR5uEUvT0ggQAS+k0ZaDcgA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

Hi Greg,

You're right, it's a bad idea. I reverted the change.

Cheers

On 08/09/2015 15:46, Gregory Farnum wrote:
> On Sun, Sep 6, 2015 at 5:04 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi,
>>
>> I wen thru all pull request looking for those not related to anything (like having "bug fix" without "core" or "rgw"). Now that there are many labels, it's not trivial for someone not used to Ceph to sort out what's what. We really have three kinds of labels:
>>
>>  * those that relate the pull request to an area / component of Ceph (rgw, core, etc.)
>>  * those used to remember at what stage of QA the pull request is (wip-* and needs*qa)
>>  * those that describe the kind of pull request (cleanup, bug fix, performance etc.)
>>
>> To help reading the label I prefixed the names of rgw, core, etc. with "related to". If someone think that's not helpful or too long to read, feel free to revert, it's just a proposal.
> 
> You broke all my bookmarked searches. :( I've updated them now but I'm
> really not sure this change is helpful — in particular, we don't need
> these labels to make sense to people who aren't used to Ceph and it's
> impossible to have them quickly auto-complete now with a long shared
> prefix across them all...
> -Greg
> 
>>
>> Cheers
>>
>> P.S. For backport snippets that set the component to "core" we'll need to change that to "related to core" instead. Not too much of an inconvenience IMHO but ...
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2015-09-08 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 16:04 pull request labels : related to Loic Dachary
2015-09-08 13:46 ` Gregory Farnum
2015-09-08 14:22   ` Loic Dachary [this message]

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=55EEEF23.10403@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.