From: "Theodore Ts'o" <tytso@mit.edu>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: rdunlap@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] Various trees,shell files missing the shebang line
Date: Tue, 22 Jul 2025 08:09:46 -0400 [thread overview]
Message-ID: <20250722120946.GC1415603@mit.edu> (raw)
In-Reply-To: <cover.1753182971.git.unixbhaskar@gmail.com>
On Tue, Jul 22, 2025 at 04:46:56PM +0530, Bhaskar Chowdhury wrote:
> This is a human being with flesh and blood.
>
> Shell script files were missing the "shebang" line aka shell interpreter.
>
> Note to Randy,
>
> This is for your spare time Eagle Eye stuff, if you could...please.
>
> Oh, I might have inadvertantly added some harmless blank lines too.
>
> Bhaskar Chowdhury (11):
> Shebang line was missing,fixed
There's also a missing space before ",fixed" in all of the commit
descriptions. Perhaps you could fix this when you send a v2?
- Ted
next prev parent reply other threads:[~2025-07-22 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 11:16 Bhaskar Chowdhury
2025-07-22 11:16 ` [PATCH 01/11] Shebang line was missing,fixed Bhaskar Chowdhury
2025-07-22 11:16 ` [PATCH 02/11] " Bhaskar Chowdhury
2025-07-22 11:16 ` [PATCH 03/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 04/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 05/11] There was a space between bang and shell path,fixed Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 06/11] Shebang line was missing,fixed Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 07/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 08/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 09/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 10/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 11/11] " Bhaskar Chowdhury
2025-07-22 12:09 ` Theodore Ts'o [this message]
2025-07-22 17:10 ` [PATCH 00/11] Various trees,shell files missing the shebang line Jonathan Corbet
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=20250722120946.GC1415603@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
/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
all inboxes | Powered by JetHome®