From: Borislav Petkov <bp@alien8.de>
To: Joe Perches <joe@perches.com>
Cc: Michal Marek <mmarek@suse.cz>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] scripts: add checkmaintainers.py
Date: Tue, 18 Dec 2012 19:28:38 +0100 [thread overview]
Message-ID: <20121218182838.GF31255@liondog.tnic> (raw)
In-Reply-To: <1355771383.13361.44.camel@joe-AO722>
On Mon, Dec 17, 2012 at 11:09:43AM -0800, Joe Perches wrote:
> This needs a new test here to avoid chirping
> on files that aren't added, deleted or renamed.
>
> next if ($realfile eq $modifiedfile);
Hmm, I don't think that catches file renames when using the normal 'git
diff' output:
$ git mv README README.old
And this detection should work in the default case with a pre-commit
hook. For example, I have this in .git/hooks/pre-commit:
if git rev-parse --verify HEAD >/dev/null 2>&1
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
fi
git diff --cached $against -- | ./scripts/checkpatch.pl --strict --no-signoff -
and when I do this, I get the changes checked:
$ git commit -a
README.old:5: trailing whitespace.
+kernel, and what to do if something goes wrong.
README.old:19: trailing whitespace.
+ accompanying COPYING file for more details.
README.old:47: trailing whitespace.
+ these typically contain kernel-specific installation notes for some
README.old:287: trailing whitespace.
+ - Keep a backup kernel handy in case something goes wrong. This is
README.old:301: trailing whitespace.
+ to the place where your regular bootable kernel is found.
README.old:314: trailing whitespace.
+ Reinstalling LILO is usually a matter of running /sbin/lilo.
README.old:317: trailing whitespace.
+ work. See the LILO docs for more information.
README.old:325: trailing whitespace.
+ recompile the kernel to change these parameters.
README.old:327: trailing whitespace.
+ - Reboot with the new kernel and enjoy.
README.old:394: trailing whitespace.
+ interesting one.
README.old:412: new blank line at EOF.
but not the MAINTAINERS check.
git diff --cached HEAD gives:
diff --git a/README b/README.old
similarity index 100%
rename from README
rename to README.old
so I'd say we're almost there.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2012-12-18 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:19 Cesar Eduardo Barros
2012-12-17 10:14 ` Michal Marek
2012-12-17 10:27 ` Borislav Petkov
2012-12-17 15:35 ` Joe Perches
2012-12-17 17:00 ` Borislav Petkov
2012-12-17 18:56 ` Joe Perches
2012-12-17 19:09 ` Joe Perches
2012-12-18 18:28 ` Borislav Petkov [this message]
2012-12-18 19:34 ` Joe Perches
2012-12-18 20:31 ` Borislav Petkov
2012-12-18 20:36 ` Joe Perches
2012-12-18 20:47 ` Borislav Petkov
2012-12-18 21:33 ` Joe Perches
2012-12-19 15:07 ` Borislav Petkov
2012-12-19 17:43 ` Joe Perches
2012-12-20 19:31 ` Borislav Petkov
2012-12-17 21:59 ` Cesar Eduardo Barros
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=20121218182838.GF31255@liondog.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dhowells@redhat.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®