From: "Ayush" <ayush@disroot.org>
To: "Joe Perches" <joe@perches.com>, apw@canonical.com
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH] checkpatch: GIT_COMMIT_ID: handle commit messages with multiple quotes
Date: Tue, 08 Sep 2020 08:32:45 +0000 [thread overview]
Message-ID: <22db634e7be36f4514f0c9b3ecf0060a@disroot.org> (raw)
In-Reply-To: <beed63208cc412f122fe273602675801add08ede.camel@perches.com>
> I think all your examples are broken.
>
> I think all should start with revert
> i.e.: Reverts commit <SHA-1> ("description...")
Actually I am talking about those commits which referenced a revert commit.
For example:
If I want to mention a revert commit in my commit message, I will do something like.
This bug appeared first in commit 1234567890ab ("Revert "abc: foo bar"").
(Just an example)
Here, according to syntax, it is right but checkpatch.pl gives an error as multiple
quotes in commit messages are not handled in checkpatch.pl.
Regards,
Ayush
_______________________________________________
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-09-08 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:14 [Linux-kernel-mentees] [PATCH] checkpatch: GIT_COMMIT_ID: handle commit messages with multiple quotes Ayush
2020-09-07 20:50 ` Joe Perches
2020-09-08 8:32 ` Ayush [this message]
2020-09-09 10:06 ` Lukas Bulwahn
2020-09-09 10:31 ` Ayush
2020-09-09 11:32 ` Lukas Bulwahn
2020-09-09 12:02 ` Joe Perches
2020-09-09 13:10 ` Lukas Bulwahn
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=22db634e7be36f4514f0c9b3ecf0060a@disroot.org \
--to=ayush@disroot.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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).