All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Nathan Lynch <nathanl@linux.ibm.com>
Cc: tools@linux.kernel.org
Subject: Re: b4 submission endpoint sender name length
Date: Thu, 23 Feb 2023 20:53:28 +1100	[thread overview]
Message-ID: <87y1ooaesn.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230222200338.sinridhdzgq2k2dd@meerkat.local>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Tue, Feb 14, 2023 at 08:40:36AM -0600, Nathan Lynch wrote:
>> Hello!
>> 
>> I've used b4 v0.12/v0.12.1 to submit kernel work to linuxppc-dev over
>> the last couple weeks and it's working very well for me. I have been
>> using the web submission endpoint.
>
> Nice!
>
>> When I checked with the powerpc maintainer (cc'd) to see if my new
>> workflow was causing any issues for him, the only less-than-positive
>> feedback I got was that the sender name set by the endpoint:
>> 
>>   Nathan Lynch via B4 Submission Endpoint
>> 
>> feels a bit long and sticks out in the patchwork UI. Could this be
>> shortened? Perhaps "via B4 web" or similar?
>
> Thank you for the feedback, I've shortened it to "B4 Relay".

Thanks.

> It won't help in
> your case, since the patchwork name is set at user record creation time and is
> then never changed even if the From: changes, but it will help others.

I can fix that as I have admin on patchwork.ozlabs.org :)

cheers

  reply	other threads:[~2023-02-23  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 14:40 b4 submission endpoint sender name length Nathan Lynch
2023-02-22 20:03 ` Konstantin Ryabitsev
2023-02-23  9:53   ` Michael Ellerman [this message]
2023-02-23 15:05   ` Nathan Lynch

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=87y1ooaesn.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=konstantin@linuxfoundation.org \
    --cc=nathanl@linux.ibm.com \
    --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 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.