[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0C18FE92A7765D4EB9EE5D38D86A563A05D1BFCA@SHSMSX103.ccr.corp.intel.com>
Date: Mon, 25 Apr 2016 02:23:17 +0000
From: "Du, Changbin" <changbin.du@...el.com>
To: Joe Perches <joe@...ches.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Whitcroft <apw@...onical.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] checkpatch: Add support to check already applied git
commits
Hi,
> From: Joe Perches [mailto:joe@...ches.com]
> Sent: Monday, April 25, 2016 7:12 AM
> To: Andrew Morton <akpm@...ux-foundation.org>; Andy Whitcroft
> <apw@...onical.com>
> Cc: Du, Changbin <changbin.du@...el.com>; linux-kernel@...r.kernel.org
> Subject: [PATCH] checkpatch: Add support to check already applied git
> commits
>
> It's sometimes useful to scan already committed patches.
>
> Add --git <revision range> to scan specific or multiple commits.
>
> Single commits are scanned with
> --git <rev>
> Multiple commits are scanned with
> --git <range>
> --git <commit>-<count>
>
> Signed-off-by: "Du, Changbin" <changbin.du@...el.com>
> Signed-off-by: Joe Perches <joe@...ches.com>
> ---
>
> A few miscellaneous improvements to Changbin's original patch:
>
> o Don't exec git for each <commit>-<count>,
> use a single "git log -<count> <commit>"
> o Consolidate the git exec for the <range> and <commit>-<count> variants
> o Output 12 character commit hash ids
> o Don't scan git commit merges
> o Use -M to reduce the size of rename commits
>
Thanks, it has been much more better now. I like this new one.
This is my first time write a Perl script. :)
Also thanks for Sebastian's explanation, I got this idea just
because I had the same use case with you.
Best Regards,
Du, Changbin
Powered by blists - more mailing lists