All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Code quality
Date: Sat, 2 May 2009 13:41:55 +0200	[thread overview]
Message-ID: <20090502114155.GE28362@thorin> (raw)
In-Reply-To: <1239833453.8204.18.camel@mj>

On Wed, Apr 15, 2009 at 06:10:53PM -0400, Pavel Roskin wrote:
> Hello!
> 
> It seems to me that the code quality has decreased in the last weeks.
> In the same time, we have a growing number of compiler warnings.  It
> looks like there is a relationship between the two.
> 
> I'll appreciate if everybody who recently contributed to GRUB looks at
> the remaining warnings and fixes at least some of them.  I don't mean
> hiding the warnings, e.g. adding casts where using different types would
> be more appropriate or initializing variables gcc claims to be
> uninitialized without making sure that gcc is indeed wrong.  But if
> there is a good fix, it should be applied.

Can we start using -Werror ?  If we can't do it globally, at least for
individual modules.  This way we gradually prevent regressions in more
areas, and (hopefully) at some point get rid of them.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-05-02 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 22:10 Code quality Pavel Roskin
2009-05-02 11:41 ` Robert Millan [this message]
2009-05-03  4:53   ` Pavel Roskin

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=20090502114155.GE28362@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.