linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>
Subject: [PATCH] scripts: Add automatic patch review script
Date: Wed,  1 Apr 2020 23:55:19 +0200	[thread overview]
Message-ID: <20200401215519.22912-1-frederic@kernel.org> (raw)

With the ever increasing volume of patches posted everyday, it has now
become hardly possible to keep up with a sane review pace, not even for
many single subsystems.

The only way to keep up to date would be to make the review process
automatic.

Now review, at a first glance, remain the last thing that can't be
automatized at all as it can only require a person to sit down and
figure out some opinion about some change.

Of course and as is often the case, an obvious and elegant solution was
waiting to be discovered. And it has been waiting since the creation of
the "Reviewed-by" tag.

All it takes is to simply generate a "Reviewed-by:" tag that you can pipe
to your favourite email sender. The script waits for a reasonably
random amount of time between each call, so that other reviewers don't
get too impressed and discouraged by how fast your CPU can make up an
opinion about a patchbomb.

Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
---
 scripts/review_patch | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 scripts/review_patch

diff --git a/scripts/review_patch b/scripts/review_patch
new file mode 100644
index 000000000000..bf08dba2bf60
--- /dev/null
+++ b/scripts/review_patch
@@ -0,0 +1,4 @@
+#!/bin/bash
+
+sleep $RANDOM
+echo "Reviewed-by: $(git config --get user.name) <$(git config --get user.email)>"
-- 
2.25.0


                 reply	other threads:[~2020-04-01 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200401215519.22912-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).