From: Mimi Zohar <zohar@linux.ibm.com>
To: THOBY Simon <Simon.THOBY@viveris.fr>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the integrity tree
Date: Tue, 24 Aug 2021 08:19:18 -0400 [thread overview]
Message-ID: <b20c9abd62a9f56f1da8a9ef22695ebbaa0499eb.camel@linux.ibm.com> (raw)
In-Reply-To: <a37d31eb-7fe6-ce46-c40a-d30654394b3f@viveris.fr>
On Tue, 2021-08-24 at 07:11 +0000, THOBY Simon wrote:
> Hi Stephen,
>
> On 8/24/21 12:18 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > c594ea470f30 ("IMA: reject unknown hash algorithms in ima_get_hash_algo")
> >
> > Fixes tag
> >
> > Fixes: 50f742dd9147 ("IMA: block writes of the security.ima xattr with
> >
> > has these problem(s):
> >
> > - Subject has leading but no trailing parentheses
> > - Subject has leading but no trailing quotes
> >
> > Please do not split FIxes tags over more than one line.
> >
>
> It's my bad, I didn't check the line wrapping when I copy/pasted the tag :/
>
> (btw checkpatch.pl doesn't detect this behavior, maybe this is something worth adding?)
>
> Is there something I can do about it?
> I don't suppose we can fix the commit, that would break the history of linux-next
> (is it maybe acceptable considering it is a "staging area"?).
>
> Sorry about that mistake,
Hi Simon,
Sorry, along with my other suggestions, adding the "Fixes" tag was sent
as a comment, which the mailer reformatted. As it is the top of the
branch, I've amended the commit and pushed it out to Korg.
For future reference, "git log --pretty=fixes -1 --abbrev=12 <commit
number>" produces the proper message. The "--abbrev" value can be set
by defining core.abbrev=12 in the git config.
thanks,
Mimi
next prev parent reply other threads:[~2021-08-24 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 22:18 linux-next: Fixes tag needs some work in the integrity tree Stephen Rothwell
2021-08-24 7:11 ` THOBY Simon
2021-08-24 12:19 ` Mimi Zohar [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 22:07 Stephen Rothwell
2021-06-01 22:54 ` Mimi Zohar
2021-05-20 22:12 Stephen Rothwell
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=b20c9abd62a9f56f1da8a9ef22695ebbaa0499eb.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=Simon.THOBY@viveris.fr \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=sfr@canb.auug.org.au \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).