public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Pop <sebpop@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Andreas.Krebbel@de.ibm.com
Subject: Script to check formatting for GNU style patches
Date: Wed, 30 Jun 2010 16:53:00 -0000	[thread overview]
Message-ID: <AANLkTilkY6FnhmrgvjGV86WS384u8SMSp_PQnTtVqtYs@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

Hi,

Some folks complained of not having a script that checks for
formatting issues in the patches to GCC.  The attached script checks
for some common formatting problems that occur in the code of new
contributors to GCC.  With time this script could be improved, but
this is already useful to avoid common mistakes.

I would like to commit this script to the contrib directory.  Ok for trunk?

Thanks,
Sebastian Pop
--
AMD / Open Source Compiler Engineering / GNU Tools

[-- Attachment #2: check_GNU_style.sh --]
[-- Type: application/x-sh, Size: 2382 bytes --]

             reply	other threads:[~2010-06-30 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 16:53 Sebastian Pop [this message]
2010-06-30 18:55 ` Diego Novillo
2010-06-30 20:09   ` Manuel López-Ibáñez
2010-06-30 21:32     ` Sebastian Pop

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=AANLkTilkY6FnhmrgvjGV86WS384u8SMSp_PQnTtVqtYs@mail.gmail.com \
    --to=sebpop@gmail.com \
    --cc=Andreas.Krebbel@de.ibm.com \
    --cc=gcc-patches@gcc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).