public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io
Cc: Philippe Mathieu-Daude <philmd@redhat.com>,
	Bob Feng <bob.c.feng@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	Laszlo Ersek <lersek@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: [PATCH 0/6] BaseTools: Improve PatchCheck and add GitPostCommitHook
Date: Thu,  5 Dec 2019 17:12:28 +0100	[thread overview]
Message-ID: <20191205161234.25071-1-philmd@redhat.com> (raw)

Hi,

This series add a script that can be use as git-post-commit
hook to run CheckPatch after each commit.

I avoided shell scripts and use Python, so it should be
usable by Visual Studio, but as I don't use it, I haven't
tested there. However it is helpful for my use case, from
a Linux console, because I won't forget to use CheckPatch
again.

In Patch #3 (GitPostCommitHook) I commented a problem with
adding CRLF scripts on Unix, we can not run them directly.

Patch #1 is actually a minor bug fix.

Regards,

Phil.

Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>

Philippe Mathieu-Daude (6):
  BaseTools/PatchCheck: Stop parsing commit message after --- separator
  BaseTools/PatchCheck: Add a --quiet option
  BaseTools/Scripts: Add GitPostCommitHook.py
  BaseTools/PatchCheck: Extract the run_git() function
  BaseTools/PatchCheck: Add printw() function to print warnings
  BaseTools/PatchCheck: Allow to print colored warnings

 BaseTools/Scripts/GitPostCommitHook.py | 21 ++++++++
 BaseTools/Scripts/PatchCheck.py        | 70 ++++++++++++++++++--------
 2 files changed, 70 insertions(+), 21 deletions(-)
 create mode 100755 BaseTools/Scripts/GitPostCommitHook.py

-- 
2.21.0


             reply	other threads:[~2019-12-05 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 16:12 Philippe Mathieu-Daudé [this message]
2019-12-05 16:12 ` [PATCH 1/6] BaseTools/PatchCheck: Stop parsing commit message after --- separator Philippe Mathieu-Daudé
2019-12-05 19:02   ` Laszlo Ersek
2019-12-05 16:12 ` [PATCH 2/6] BaseTools/PatchCheck: Add a --quiet option Philippe Mathieu-Daudé
2019-12-05 16:12 ` [PATCH 3/6] BaseTools/Scripts: Add GitPostCommitHook.py Philippe Mathieu-Daudé
2019-12-05 19:24   ` Laszlo Ersek
2019-12-05 16:12 ` [PATCH 4/6] BaseTools/PatchCheck: Extract the run_git() function Philippe Mathieu-Daudé
2019-12-05 16:12 ` [PATCH 5/6] BaseTools/PatchCheck: Add printw() function to print warnings Philippe Mathieu-Daudé
2019-12-05 16:12 ` [PATCH 6/6] BaseTools/PatchCheck: Allow to print colored warnings Philippe Mathieu-Daudé

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-list 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=20191205161234.25071-1-philmd@redhat.com \
    --to=devel@edk2.groups.io \
    /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