| 1 |
Hi! |
| 2 |
|
| 3 |
On Sun, 09 Aug 2015, Sven Vermeulen wrote: |
| 4 |
|
| 5 |
> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote: |
| 6 |
> > > I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that |
| 7 |
> > > parse commit messages. |
| 8 |
> > |
| 9 |
> > I don't. Just the "bug " prefix should be fine for almost all |
| 10 |
> > purposes, even for tools. |
| 11 |
> |
| 12 |
> I'm pretty sure the majority of developers don't care that one developer |
| 13 |
> uses "X-Gentoo-Bug" and another just adds it to the commit title. |
| 14 |
> |
| 15 |
> I like /guidelines/ in the sense that, if I don't know something, I can look |
| 16 |
> it up. But don't make it mandatory until we start depending on it (for |
| 17 |
> instance, when we would automate stuff based on the content of the commit |
| 18 |
> message). |
| 19 |
|
| 20 |
I'd just go with "Gentoo-Bug". The X- is pointless since it was |
| 21 |
for eXtending Email-Headers. And what we do is only linked in |
| 22 |
style. |
| 23 |
|
| 24 |
Regards, |
| 25 |
Tobias |
| 26 |
|
| 27 |
-- |
| 28 |
Sent from aboard the Culture ship |
| 29 |
(ex) General Transport Craft (Interstellar-class) Now We Try It My Way |
Archives