All of lore.kernel.org
 help / color / mirror / Atom feed
From: konstantin.ryabitsev@linux.dev
To: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	patches@lists.linux.dev
Subject: Re: [PATCH WIP v1 0/3] Fake series to test out b4 submit
Date: Fri, 15 Jul 2022 15:39:25 +0000	[thread overview]
Message-ID: <54c0f98fb45e28e865055e766c3245ab@linux.dev> (raw)
In-Reply-To: <20220707-my-new-branch-v1-0-8d355bae1bb5@linuxfoundation.org>

July 14, 2022 3:52 PM, "Konstantin Ryabitsev" <konstantin@linuxfoundation.org> wrote:
> This is a fake series that I created to test b4 submit. It will be sent
> to the patches list, but it's not a real set of patches. You can ignore
> everything about it.
> 
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> Suggested-by: Sockpuppet Squirrel <mricon@gmail.com>

This is a cover letter trailer with a mismatched From.

Tested-by: Mister Mismatchy <mricon@kernel.org>

-K

      parent reply	other threads:[~2022-07-15 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 19:52 [PATCH WIP v1 0/3] Fake series to test out b4 submit Konstantin Ryabitsev
2022-07-14 19:52 ` [PATCH WIP v1 1/3] Rename Linux into Konix Konstantin Ryabitsev
2022-07-15 15:40   ` konstantin.ryabitsev
2022-07-14 19:52 ` [PATCH WIP v1 2/3] Our version goes to 11 Konstantin Ryabitsev
2022-07-14 19:52 ` [PATCH WIP v1 3/3] Add myself as ultimate maintainer Konstantin Ryabitsev
2022-07-14 20:02   ` Ammar Faizi
2022-07-14 20:05     ` Ammar Faizi
2022-07-14 20:07       ` Konstantin Ryabitsev
2022-07-14 20:40         ` Ammar Faizi
2022-07-14 21:01           ` Konstantin Ryabitsev
2022-07-14 20:11     ` Ammar Faizi
2022-07-14 20:11       ` Ammar Faizi
2022-07-14 21:00     ` Konstantin Ryabitsev
2022-07-15 15:08 ` [PATCH WIP v1 0/3] Fake series to test out b4 submit Konstantin Ryabitsev
2022-07-15 15:39 ` 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=54c0f98fb45e28e865055e766c3245ab@linux.dev \
    --to=konstantin.ryabitsev@linux.dev \
    --cc=konstantin@linuxfoundation.org \
    --cc=patches@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.