Linux maintainer tooling and workflows
 help / color / Atom feed
* Tags placed incorrectly in malformed messages
@ 2020-06-08 11:46 Mark Brown
  2020-06-08 16:30 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 2+ messages in thread
From: Mark Brown @ 2020-06-08 11:46 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools


[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

Hi,

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,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Tags placed incorrectly in malformed messages
  2020-06-08 11:46 Tags placed incorrectly in malformed messages Mark Brown
@ 2020-06-08 16:30 ` Konstantin Ryabitsev
  0 siblings, 0 replies; 2+ messages in thread
From: Konstantin Ryabitsev @ 2020-06-08 16:30 UTC (permalink / raw)
  To: Mark Brown; +Cc: tools

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-08 11:46 Tags placed incorrectly in malformed messages Mark Brown
2020-06-08 16:30 ` Konstantin Ryabitsev

Linux maintainer tooling and workflows

Archives are clonable:
	git clone --mirror https://lore.kernel.org/tools/0 tools/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 tools tools/ https://lore.kernel.org/tools \
		tools@linux.kernel.org
	public-inbox-index tools

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.linux.tools


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git