| 1 |
On Wed, Jul 26, 2017 at 07:05:47PM +0200, Kristian Fiskerstrand wrote: |
| 2 |
> On 07/25/2017 02:28 PM, Michael Palimaka wrote: |
| 3 |
> > Does a bug # really need to always be in the summary line? It can eat |
| 4 |
> > valuable characters and tags which are pretty popular are equally valid IMO. |
| 5 |
> |
| 6 |
> I would prefer the summary to be informative without having bug ID at |
| 7 |
> all. Summary should describe the change ,not only "fixes XXX", the bug |
| 8 |
> reference belongs in body (tags) |
| 9 |
> |
| 10 |
> -- |
| 11 |
> Kristian Fiskerstrand |
| 12 |
> OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 13 |
> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
| 14 |
|
| 15 |
+1 |
| 16 |
|
| 17 |
Given the length restriction and the requirement to include |
| 18 |
category/package, adding a bug reference doesn't leave much space for a |
| 19 |
useful description. |
| 20 |
|
| 21 |
-- |
| 22 |
Sam Jorna (wraeth) |
| 23 |
GnuPG Key: D6180C26 |
Archives