Gentoo Archives: gentoo-dev

From: hasufell <hasufell@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 15:07:09
Message-Id: 55C76C91.8040302@gentoo.org
In Reply to: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) by Sven Vermeulen
1 On 08/09/2015 05:03 PM, Sven Vermeulen wrote:
2 > On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
3 >>> I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
4 >>> parse commit messages.
5 >>
6 >> I don't. Just the "bug " prefix should be fine for almost all
7 >> purposes, even for tools.
8 >
9 > I'm pretty sure the majority of developers don't care that one developer
10 > uses "X-Gentoo-Bug" and another just adds it to the commit title.
11 >
12 > I like /guidelines/ in the sense that, if I don't know something, I can look
13 > it up. But don't make it mandatory until we start depending on it (for
14 > instance, when we would automate stuff based on the content of the commit
15 > message).
16 >
17
18 At the time we decide to depend on it, it will already be useless for
19 the complete past history, because some people did it... and others not.
20
21 Deciding on such things early on is a good idea, especially for a
22 project as big as gentoo. That is... if we want our history to be useful.