From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings )
Date: Tue, 12 Aug 2014 12:36:10 -0400 [thread overview]
Message-ID: <CAGfcS_kF+fydeR+f=Lazte+N7kvzFMz8TLcwNoM+JfquAhOwjw@mail.gmail.com> (raw)
In-Reply-To: <53EA1F0A.8010907@gentoo.org>
On Tue, Aug 12, 2014 at 10:04 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
>
> I'm wondering what everyone thinks of having a --nonag option to
> repoman and shoving some of the more trivial/style-related repoman
> 'warnings' into a 'nag' level warning? IIRC at least one of the QA
> team members is so tired of the warnings that they want to make every
> single one of them errors; the --nonag option would allow those
> warnings to remain in repoman (ie to help guide new dev's or non-dev's
> using repoman on their local repos) but since they don't relate to
> actual technical breakage they can just be turned off during QA runs, etc.
>
What, specifically, are we considering trivial?
The whole point of repoman is to prevent devs from making mistakes.
Being able to turn off warnings is counterproductive. Eliminating
warnings that don't need to be warnings is of course fine.
There is no value in having an escalating battle between warnings and
options to suppress them.
Rich
next prev parent reply other threads:[~2014-08-12 16:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 12:22 [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Sergei Trofimovich
2014-08-11 20:34 ` Bertrand Jacquin
2014-08-12 18:32 ` Michał Górny
2014-08-12 1:48 ` William Hubbs
2014-08-12 1:59 ` Manuel Rüger
2014-08-12 2:42 ` William Hubbs
2014-08-12 4:20 ` Tyler Pohl
2014-08-12 5:29 ` [gentoo-dev] " Duncan
2014-08-12 11:33 ` Alex Xu
2014-08-12 12:47 ` [gentoo-dev] " hasufell
2014-08-12 13:26 ` Rich Freeman
2014-08-12 14:26 ` hasufell
2014-08-12 16:24 ` William Hubbs
2014-08-12 18:37 ` Chris Reffett
2014-08-12 21:08 ` hasufell
2014-08-12 13:54 ` Ian Stakenvicius
2014-08-12 14:04 ` [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings ) Ian Stakenvicius
2014-08-12 16:36 ` Rich Freeman [this message]
2014-08-12 16:57 ` Ian Stakenvicius
2014-08-12 17:08 ` hasufell
2014-08-12 17:13 ` Ian Stakenvicius
2014-08-12 17:25 ` Rich Freeman
2014-08-12 17:46 ` William Hubbs
2014-08-12 19:01 ` Michał Górny
2014-08-12 19:11 ` Ian Stakenvicius
2014-08-13 8:47 ` Tom Wijsman
2014-08-12 18:46 ` [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Michał Górny
2014-08-18 14:10 ` Ben de Groot
2014-08-13 8:38 ` Tom Wijsman
2014-08-13 16:36 ` [gentoo-dev] " Duncan
2014-08-12 22:00 ` [gentoo-dev] " Alexander Berntsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_kF+fydeR+f=Lazte+N7kvzFMz8TLcwNoM+JfquAhOwjw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox