Gentoo Archives: gentoo-dev

From: Kent Fredric <kentfredric@×××××.com>
To: gentoo-dev <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: Mon, 10 Aug 2015 00:10:27
Message-Id: CAATnKFDnn60k+7fBFBFs1LRV6GoqiqKZtGSYuK08ByTPuzy+Ow@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 hasufell
1 On 10 August 2015 at 11:46, hasufell <hasufell@g.o> wrote:
2 > As I see it, a lot of people already stuff the bug number into the
3 > summary and I can't really say anything against that. It gives a nice
4 > overview when you look at it:
5 > https://gitweb.gentoo.org/repo/gentoo.git/log/
6 >
7 > Given that fact, I am not sure we can convince people to repeat the bug
8 > number in the description of the commit. However, the bug url definitely
9 > does not fit into the summary, but in the description. That would be an
10 > argument for the bug url thing (so we actually have both
11
12
13 Its also "nice" to see that in #gentoo-commits, becasue it triggers
14 wilkins to automatically fetch and display the summary of the
15 referenced bug, expanding the context.
16
17 That behaviour is not *always* nice ( ie: dozens of commits doing
18 keywording gets a bit spammy sometimes ), but used well it is nice.
19
20 Doing that with a Gentoo-Bug: <URL> or similar means we have to
21 enhance the commit reporting drone to give that context if that
22 behaviour is deemed desirable.
23
24 --
25 Kent
26
27 KENTNL - https://metacpan.org/author/KENTNL