From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: tools@linux.kernel.org
Subject: Re: feature request: b4 send should print lore link
Date: Mon, 1 May 2023 11:42:02 -0400 [thread overview]
Message-ID: <20230501-quickly-canola-1f487e@meerkat> (raw)
In-Reply-To: <CAKwvOdnsFk4zV24SDUf1iBYwTT=7eVKRxoKyJYkVnwqw_dbmzw@mail.gmail.com>
On Fri, Apr 28, 2023 at 11:15:01AM -0700, Nick Desaulniers wrote:
> Instead of "Recording series message-id in cover letter tracking"
> maybe "Sent to https://lore.kernel.org/all/20230428-awx-v1-1-1f490286ba62@google.com/"
> (or in addition)?
I don't really have any specific objections to doing this, other than that the
link will go nowhere for the first 5-10 minutes due to SMTP and lore
replication delays. My worry is that this will make someone think that
something didn't work and they need to resend.
I'll see what makes sense here.
-K
prev parent reply other threads:[~2023-05-01 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 18:15 feature request: b4 send should print lore link Nick Desaulniers
2023-05-01 15:42 ` 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=20230501-quickly-canola-1f487e@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=ndesaulniers@google.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 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).