From: Nathan Lynch <nathanl@linux.ibm.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: b4 submission endpoint sender name length
Date: Thu, 23 Feb 2023 09:05:46 -0600 [thread overview]
Message-ID: <87wn488lrp.fsf@linux.ibm.com> (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:
>> 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 a lot!
prev parent reply other threads:[~2023-02-23 15:05 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
2023-02-23 15:05 ` Nathan Lynch [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=87wn488lrp.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=konstantin@linuxfoundation.org \
--cc=mpe@ellerman.id.au \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).