Messages in this thread | | | From | "Du, Changbin" <> | Subject | RE: [PATCH] checkpatch: Add support to check already applied git commits | Date | Mon, 25 Apr 2016 02:23:17 +0000 |
| |
Hi,
> From: Joe Perches [mailto:joe@perches.com] > Sent: Monday, April 25, 2016 7:12 AM > To: Andrew Morton <akpm@linux-foundation.org>; Andy Whitcroft > <apw@canonical.com> > Cc: Du, Changbin <changbin.du@intel.com>; linux-kernel@vger.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@intel.com> > Signed-off-by: Joe Perches <joe@perches.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
| |