From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
zlang@kernel.org, david@fromorbit.com,
nirjhar.roy.lists@gmail.com
Subject: [PATCH v1 1/3] new: Add a new parameter (name/emailid) in the "new" script
Date: Tue, 13 May 2025 08:10:10 +0000 [thread overview]
Message-ID: <837f220a24b8cbaaaeb2bc91287f2d7db930001a.1747123422.git.nirjhar.roy.lists@gmail.com> (raw)
In-Reply-To: <cover.1747123422.git.nirjhar.roy.lists@gmail.com>
This patch another optional interactive prompt to enter the
author name and email id for each new test file that is
created using the "new" file.
The sample output looks like something like the following:
./new selftest
Next test id is 007
Append a name to the ID? Test name will be 007-$name. y,[n]:
Creating test file '007'
Add to group(s) [auto] (separate by space, ? for list): selftest quick
Enter <author_name> <email-id>: Nirjhar Roy <nirjhar.roy.lists@gmail.com>
Creating skeletal script for you to edit ...
done.
...
...
Signed-off-by: Nirjhar Roy (IBM) <nirjhar.roy.lists@gmail.com>
---
new | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/new b/new
index 6b50ffed..139715bf 100755
--- a/new
+++ b/new
@@ -136,6 +136,9 @@ else
check_groups "${new_groups[@]}" || exit 1
fi
+read -p "Enter <author_name> <email-id>: " -r
+author_name="${REPLY:=YOUR NAME HERE}"
+
echo -n "Creating skeletal script for you to edit ..."
year=`date +%Y`
@@ -143,7 +146,7 @@ year=`date +%Y`
cat <<End-of-File >$tdir/$id
#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
-# Copyright (c) $year YOUR NAME HERE. All Rights Reserved.
+# Copyright (c) $year $author_name. All Rights Reserved.
#
# FS QA Test $id
#
--
2.34.1
next prev parent reply other threads:[~2025-05-13 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:10 [PATCH v1 0/3] new: Improvements to new script Nirjhar Roy (IBM)
2025-05-13 8:10 ` Nirjhar Roy (IBM) [this message]
2025-05-14 5:36 ` [PATCH v1 1/3] new: Add a new parameter (name/emailid) in the "new" script Zorro Lang
2025-05-14 6:39 ` Nirjhar Roy (IBM)
2025-05-13 8:10 ` [PATCH v1 2/3] new: Replace "status=0; exit 0" with _exit 0 Nirjhar Roy (IBM)
2025-05-14 5:20 ` Zorro Lang
2025-05-13 8:10 ` [PATCH v1 3/3] new: Run make after adding a new test file Nirjhar Roy (IBM)
2025-05-14 5:16 ` Zorro Lang
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=837f220a24b8cbaaaeb2bc91287f2d7db930001a.1747123422.git.nirjhar.roy.lists@gmail.com \
--to=nirjhar.roy.lists@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=zlang@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).