From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
ojaswin@linux.ibm.com, djwong@kernel.org, zlang@kernel.org
Subject: Re: [PATCH v2 1/2] new: Add a new parameter (name/emailid) in the "new" script
Date: Wed, 21 May 2025 10:52:22 +0530 [thread overview]
Message-ID: <12e307e0-2a28-4a42-a8b3-d2186c871be7@gmail.com> (raw)
In-Reply-To: <aC0Q2HIesHMXqVLG@dread.disaster.area>
On 5/21/25 05:01, Dave Chinner wrote:
> On Thu, May 15, 2025 at 11:00:16AM +0000, Nirjhar Roy (IBM) wrote:
>> 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..636648e2 100755
>> --- a/new
>> +++ b/new
>> @@ -136,6 +136,9 @@ else
>> check_groups "${new_groups[@]}" || exit 1
>> fi
>>
>> +read -p "Enter <author_name>: " -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.
> In many cases, this is incorrect.
>
> For people who are corporate employees, copyright for the code they
> write is typically owned by their employer, not the employee who
> wrote the code. i.e. this field generally contains something like
> "Red Hat, Inc", "Oracle, Inc", "IBM Corporation", etc in these
> cases, not the employee's name.
Yes. The existing placeholder is already "YOUR NAME HERE" (which I have
kept unchanged). The author can always use the company's name from read
-p prompt or simply chose to fill it up later, right? Or are you saying
that the existing placeholder "YOUR NAME HERE" is incorrect?
--NR
>
> -Dave.
--
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore
next prev parent reply other threads:[~2025-05-21 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 11:00 [PATCH v2 0/2] new: Improvements to new script Nirjhar Roy (IBM)
2025-05-15 11:00 ` [PATCH v2 1/2] new: Add a new parameter (name/emailid) in the "new" script Nirjhar Roy (IBM)
2025-05-17 2:48 ` Ritesh Harjani
2025-05-19 5:21 ` Nirjhar Roy (IBM)
2025-05-20 23:31 ` Dave Chinner
2025-05-21 5:22 ` Nirjhar Roy (IBM) [this message]
2025-05-22 0:51 ` Dave Chinner
2025-05-22 4:50 ` Nirjhar Roy (IBM)
2025-05-15 11:00 ` [PATCH v2 2/2] new: Replace "status=0; exit 0" with _exit 0 Nirjhar Roy (IBM)
2025-05-17 5:58 ` Ritesh Harjani
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=12e307e0-2a28-4a42-a8b3-d2186c871be7@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