All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Luis R. Rodriguez" <lrodriguez@Atheros.com>
Cc: <joe@perches.com>, <torvalds@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>, <mcgrof@gmail.com>
Subject: Re: [PATCH 3/3] checkincludes.pl: add option to remove duplicates in place
Date: Wed, 5 Aug 2009 18:59:45 -0700	[thread overview]
Message-ID: <20090805185945.1ece6088.akpm@linux-foundation.org> (raw)
In-Reply-To: <1249519872-23958-4-git-send-email-lrodriguez@atheros.com>

On Wed, 5 Aug 2009 17:51:12 -0700 "Luis R. Rodriguez" <lrodriguez@Atheros.com> wrote:

> checkincludes.pl is more useful if it actually removed
> the lines. This adds support for that with -r.
> 

hm, spose so.  It can't do any harm.

Plus it's about time we edited that file - it hasn't been changed since
we started the bk tree.


> ---
>  scripts/checkincludes.pl |   57 +++++++++++++++++++++++++++++++++++++++++-----
>  1 files changed, 51 insertions(+), 6 deletions(-)
> 
> diff --git a/scripts/checkincludes.pl b/scripts/checkincludes.pl
> index 4bff139..5a53407 100755
> --- a/scripts/checkincludes.pl
> +++ b/scripts/checkincludes.pl
> @@ -2,32 +2,77 @@
>  #
>  # checkincludes: Find files included more than once in (other) files.
>  # Copyright abandoned, 2000, Niels Kristian Bech Jensen <nkbj@image.dk>.
> +# Copyright abandoned, 2009, Luis R. Rodriguez <mcgrof@gmail.com>
>  
>  sub usage {
> -	print "Usage: checkincludes.pl <file list>\n";
> +	print "Usage: checkincludes.pl [-r]\n";
> +	print "By default we just warn of duplicates\n";
> +	print "To remove files in place use -r\n";

I'm not sure I like the wording here - I don't _want_ my files removed!

This?

--- a/scripts/checkincludes.pl~checkincludespl-add-option-to-remove-duplicates-in-place-fix
+++ a/scripts/checkincludes.pl
@@ -7,7 +7,7 @@
 sub usage {
 	print "Usage: checkincludes.pl [-r]\n";
 	print "By default we just warn of duplicates\n";
-	print "To remove files in place use -r\n";
+	print "To remove duplicated includes in place use -r\n";
 	exit 1;
 }
 
_


  reply	other threads:[~2009-08-06  2:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  0:51 [PATCH 0/3] checkincludes.pl: add removal option Luis R. Rodriguez
2009-08-06  0:51 ` [PATCH 1/3] checkincludes.pl: close file as soon as we're done with it Luis R. Rodriguez
2009-08-06  0:51 ` [PATCH 2/3] checkincludes.pl: provide usage helper Luis R. Rodriguez
2009-08-06  0:51 ` [PATCH 3/3] checkincludes.pl: add option to remove duplicates in place Luis R. Rodriguez
2009-08-06  1:59   ` Andrew Morton [this message]
2009-08-06  2:10     ` Luis R. Rodriguez
2009-08-06 19:17     ` Daniel K.

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=20090805185945.1ece6088.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrodriguez@Atheros.com \
    --cc=mcgrof@gmail.com \
    --cc=torvalds@linux-foundation.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.