tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: Tags placed incorrectly in malformed messages
Date: Mon, 8 Jun 2020 12:30:53 -0400	[thread overview]
Message-ID: <20200608163053.ut4aqjhtoc3mszhb@chatter.i7.local> (raw)
In-Reply-To: <20200608114630.GE4593@sirena.org.uk>

On Mon, Jun 08, 2020 at 12:46:30PM +0100, Mark Brown wrote:
> When fetching the message 20200606153103.GA17905@amd b4 picks up the
> fact that there's a Reviewed-by but places it at the end of the message
> after the body of the patch.  This seems to be triggered by the fact
> that the patch submission is not in a standard format, lacking the ---
> separator after the commit log.

Thanks for the report. I committed a fix into master and stable-0.5.y 
that deals with this case.

Best,
-K

      reply	other threads:[~2020-06-08 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 11:46 Tags placed incorrectly in malformed messages Mark Brown
2020-06-08 16:30 ` Konstantin Ryabitsev [this message]

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=20200608163053.ut4aqjhtoc3mszhb@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=tools@linux.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).