public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: 'stricter' FEATURE and "poor programming   practices" notice
Date: Thu, 17 May 2007 21:05:01 -0600	[thread overview]
Message-ID: <f2j54u$hke$1@sea.gmane.org> (raw)
In-Reply-To: <20070517122350.6cd95be9@snowflake>

Ciaran McCreesh wrote:
> Hans de Graaff <graaff@gentoo.org> wrote:

>> My view is that if this is a QA notice then, if a package doesn't
>> emerge because of it, it is a Gentoo QA bug and package maintainers
>> should be responsible for fixing it. 

> Gentoo should not be applying patches simply to fix what certain people
> consider to be 'poor programming practises', since such practices are
> not in themselves bugs. Under certain circumstances it's appropriate to
> notify upstream about such issues, but be aware that upstream may not
> take kindly to external attempts to impose arbitrary coding standards
> if there is no actual problem.

Especially considering the large number of false positives certain -W
options generate.  Compiler warnings should be for upstream and
developers doing debugging to worry about, not downstream QA or our users.


-- 
                                where to now? if i had to guess
dirtyepic gentoo org        i'm afraid to say antarctica's next
9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-05-18  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 11:12 [gentoo-dev] 'stricter' FEATURE and "poor programming practices" notice Hans de Graaff
2007-05-17 11:23 ` Ciaran McCreesh
2007-05-18  3:05   ` Ryan Hill [this message]
2007-05-17 19:50 ` Zac Medico
2007-05-19 15:32 ` Kevin F. Quinn

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='f2j54u$hke$1@sea.gmane.org' \
    --to=dirtyepic@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