1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA1
|
3 |
|
4 |
On Tue, 12 Aug 2014 10:04:58 -0400
|
5 |
Ian Stakenvicius <axs@g.o> wrote:
|
6 |
|
7 |
> I'm wondering what everyone thinks of having a --nonag option to |
8 |
> repoman and shoving some of the more trivial/style-related repoman |
9 |
> 'warnings' into a 'nag' level warning? |
10 |
|
11 |
What is the point of a repoman 'warning' if it doesn't nag anymore?
|
12 |
|
13 |
> IIRC at least one of the QA team members is so tired of the warnings |
14 |
> that they want to make every single one of them errors; the --nonag |
15 |
> option would allow those warnings to remain in repoman (ie to help |
16 |
> guide new dev's or non-dev's using repoman on their local repos) but |
17 |
> since they don't relate to actual technical breakage they can just be |
18 |
> turned off during QA runs, etc. |
19 |
|
20 |
For all I know the QA team tries to get rid of them where we can with
|
21 |
the resources available; we're not necessarily tired of seeing them, but
|
22 |
what is the point in having such repoman 'warning' if maintainers as a
|
23 |
whole don't pursue the same goal as the QA team is trying to do here?
|
24 |
|
25 |
These repoman warnings don't block commits; so, they're not problematic
|
26 |
in terms of being able to do your workflow. There has been talk by
|
27 |
Patrick to turn some of the warnings into errors, but that doesn't imply
|
28 |
that the QA team or community necessarily thinks in the same way.
|
29 |
|
30 |
So, I don't think that's something to worry about; especially with the
|
31 |
increased awareness after the DESCRIPTION.punctuation happening.
|
32 |
|
33 |
- --
|
34 |
With kind regards,
|
35 |
|
36 |
Tom Wijsman (TomWij)
|
37 |
Gentoo Developer
|
38 |
|
39 |
E-mail address : TomWij@g.o
|
40 |
GPG Public Key : 6D34E57D
|
41 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
|
42 |
-----BEGIN PGP SIGNATURE-----
|
43 |
Version: GnuPG v2
|
44 |
|
45 |
iQEcBAEBAgAGBQJT6yY7AAoJEPWZc8roOL/Q9YcH/1uQ4yxS19X/EKb0x3RZWK5M
|
46 |
Yk3HRJoFidD1q0mcVhqmYs8ZU+y6kppE3yHw0hpPMt3yEzym9ObB+EFl8C4841cr
|
47 |
3wlyY4hLNjn+hHvgiZMi3c2+OTiKZB02z7sZ/gRb5Q0oWWINZn7buWGvI0Y2iuk/
|
48 |
URKjn73yPsg4EisPDrfpX8NdHqSZP5MV1/EFibU0zmd97L0O/mcB/UvTOMQYegyL
|
49 |
NEE9hLPcrU9BTl4KYsRCDhqssKu7RFsMtbuzHHrswmSMUtPtUcjeVt5EFTjYt+0k
|
50 |
lzDEGREh9kYd87vapeUmShTZXJcK8TnwDDwh2qbNcc+M8fgOoqTbR1rmOiIjFwA=
|
51 |
=cFld
|
52 |
-----END PGP SIGNATURE----- |