From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E29E213877A for ; Tue, 12 Aug 2014 19:11:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8D19CE0D21; Tue, 12 Aug 2014 19:11:23 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6D020E0D1B for ; Tue, 12 Aug 2014 19:11:22 +0000 (UTC) Received: from [192.168.1.195] (CPE002401f30b73-CM78cd8ec1b205.cpe.net.cable.rogers.com [99.224.181.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id 30DC73404AF for ; Tue, 12 Aug 2014 19:11:21 +0000 (UTC) Message-ID: <53EA66D1.7070307@gentoo.org> Date: Tue, 12 Aug 2014 15:11:13 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev Subject: Re: [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings ) References: <20140810152211.2cc5ae94@sf> <20140812014820.GA3086@linux1> <53E97502.40604@gentoo.org> <20140812024257.GA3262@linux1> <53EA0CC6.6050000@gentoo.org> <53EA1C86.6070800@gentoo.org> <53EA1F0A.8010907@gentoo.org> <20140812210121.0d2b52ca@pomiot.lan> In-Reply-To: <20140812210121.0d2b52ca@pomiot.lan> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Archives-Salt: 3283c9ec-b810-4a43-b0f5-4437b3db7d13 X-Archives-Hash: 26ea69fb64aec843ed2022ae069dee62 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/08/14 03:01 PM, Michał Górny wrote: > Dnia 2014-08-12, o godz. 10:04:58 Ian Stakenvicius > napisał(a): >> On 12/08/14 09:54 AM, Ian Stakenvicius wrote: >>> >>> Perhaps we need to have a less-important repoman warning level >>> (something that can be quieted with a flag) for things like >>> this? In terms of DESCRIPTION consistency I don't see it being >>> a bad thing that we have the warning, but i also don't see a >>> point in changing the entire tree to get rid of 3000 bytes, >>> esp. since the ChangeLog entries added to the tree will add at >>> least 30,000 bytes :) >>> >> >> 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. > > Just don't. I think you missed the point hard and I don't want to > know where the ricochet ended. The ricochet more or less ended with the notion that repoman shouldn't be a random style guide, or rather, development time is better spent elsewhere rather than making it into one -- and so there's no use case for "nag" level messages and a flag that would disable them. > Thirdly, I'm pretty sure I had a third argument but I forgot what > it was. But it was totally convincing, I'm sure of it. Yep, that one was definitely the clincher. you've convinced me! :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlPqZtEACgkQ2ugaI38ACPCDBAD/WJQ8JBPnYD5XuqTMqHygYd5L K24oZzyhAsR1vkSahhgBAIW+hia5MXJd4T4AD8u9hi4xzdxGg/2xpwlYMs0u9VQ8 =vQMn -----END PGP SIGNATURE-----