From: Peilin Ye <yepeilin.cs@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Possible new warning for checkpatch
Date: Mon, 30 Nov 2020 10:23:29 -0500 [thread overview]
Message-ID: <20201130152329.GA25773@PWN> (raw)
In-Reply-To: <CABJPP5CZhURjFi9xE9KpxKSygS2z_8pbnrvhvV0nQGP9+vZ5_g@mail.gmail.com>
On Mon, Nov 30, 2020 at 08:28:23PM +0530, Dwaipayan Ray wrote:
> Hi Lukas,
> I was having a talk with Peilin and a possible new idea came up.
> It's about lines in the commit message that start with a '#'.
>
> Normally if a patch contains lines starting with '#' in the commit
> message, when they are applied they successfully appear in the
> git log. But if a maintainer for some reason decides to rebase and
> reword the commit message for whatever reason, the # lines are gone.
Thanks for bringing this up Dwaipayan!
Yes, for example, if one included some code examples (e.g. `#define ...`)
in the commit message, then the maintainer applied, and reworded the
commit to add their own Signed-off-by:, then all the # lines are gone.
> Peilin had a look at it and he was able to successfully reproduce this
> fault.
>
> Now would it make sense if a warning for such lines starting with '#' in
> the commit message are emitted by checkpatch itself? I have no idea
> what other developers do, so I could be wrong at this point. But I would
> like your opinion.
I admit it is a beginner's mistake, but I myself learned it in a hard
way (i.e. by having a patch mainline'd then seeing these # lines gone),
so personally I hope this becomes a new feature of checkpatch.
Thank you,
Peilin Ye
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-11-30 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:58 [Linux-kernel-mentees] Possible new warning for checkpatch Dwaipayan Ray
2020-11-30 15:23 ` Peilin Ye [this message]
2020-11-30 15:51 ` Lukas Bulwahn
2020-11-30 16:13 ` Peilin Ye
2020-11-30 16:16 ` Dwaipayan Ray
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=20201130152329.GA25773@PWN \
--to=yepeilin.cs@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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