| 1 |
On 07/25/2017 01:25 PM, Michael Orlitzky wrote: |
| 2 |
> There are two main advantages over having the bug number in the summary. |
| 3 |
> Space is at a premium in the summary, as Tobias pointed out, and the |
| 4 |
> |
| 5 |
> Gentoo-Bug: whatever |
| 6 |
> |
| 7 |
> format is trivially machine-readable, whereas sticking it somewhere else |
| 8 |
> is less so. |
| 9 |
|
| 10 |
Indeed, I'm in favor of keeping bug information in this format, whereby |
| 11 |
Bug: <URL> is fine as a generic reference it will mostly be for upstream |
| 12 |
issues or other distributions, whereby Gentoo-Bug: #nnnnnn is explicit |
| 13 |
reference to our own tracker. An issue to consider is definition of this |
| 14 |
label in terms of whether it takes a single value or a list and how to |
| 15 |
do wrapping.. I'd likely expect possibility for multiple occurrences for |
| 16 |
it but allowing multiple bug numbers specified comma separated |
| 17 |
|
| 18 |
-- |
| 19 |
Kristian Fiskerstrand |
| 20 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 21 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives