Gentoo Archives: gentoo-dev

From: Davide Pesavento <pesa@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/)
Date: Sun, 09 Aug 2015 18:49:57
Message-Id: CADfzvvbeZ5iT_XG+YaCLxjwQL=JON6OLKyXoH2hpn8mXxcpyPw@mail.gmail.com
In Reply to: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) by Mike Gilbert
1 On Sun, Aug 9, 2015 at 8:43 AM, Mike Gilbert <floppym@g.o> wrote:
2 > On Sun, Aug 9, 2015 at 11:30 AM, hasufell <hasufell@g.o> wrote:
3 >> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
4 >>> Hi!
5 >>>
6 >>> On Sun, 09 Aug 2015, Sven Vermeulen wrote:
7 >>>
8 >>>> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
9 >>>>>> I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
10 >>>>>> parse commit messages.
11 >>>>>
12 >>>>> I don't. Just the "bug " prefix should be fine for almost all
13 >>>>> purposes, even for tools.
14 >>>>
15 >>>> I'm pretty sure the majority of developers don't care that one developer
16 >>>> uses "X-Gentoo-Bug" and another just adds it to the commit title.
17 >>>>
18 >>>> I like /guidelines/ in the sense that, if I don't know something, I can look
19 >>>> it up. But don't make it mandatory until we start depending on it (for
20 >>>> instance, when we would automate stuff based on the content of the commit
21 >>>> message).
22 >>>
23 >>> I'd just go with "Gentoo-Bug". The X- is pointless since it was
24 >>> for eXtending Email-Headers. And what we do is only linked in
25 >>> style.
26 >>>
27 >>
28 >> I'd be fine with that and add a reference to the kernel guideline [0] to
29 >> the wiki as well, so that it is clear that we also allow/use Acked-by,
30 >> Reviewed-by, Suggested-by and whatnot.
31 >>
32 >> I'll wait for more ++ though.
33 >
34 > I like Gentoo-Bug. Much nicer without the X-.
35 >
36
37 +1 for Gentoo-Bug (or Gentoo-bug? not sure about the capitalization)

Replies