From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: Re: Tag for upcoming nolibc pull request
Date: Tue, 26 Jul 2022 21:32:53 +0200 [thread overview]
Message-ID: <20220726193253.GA16812@1wt.eu> (raw)
In-Reply-To: <20220726184328.GA3404553@paulmck-ThinkPad-P17-Gen-1>
Hello Paul,
On Tue, Jul 26, 2022 at 11:43:28AM -0700, Paul E. McKenney wrote:
> Hello!
>
> I have pushed out a signed nolibc pull request tag "nolibc.2022.07.27a"
> on the -rcu tree, as shown below.
>
> Please let me know if I should make changes to the tag's title or body.
>
> If I don't hear otherwise by Friday morning (July 29th), Pacific Time,
> I will use this tag for my nolibc pull request to Linus.
That's pretty fine by me, thank you!
Willy
next prev parent reply other threads:[~2022-07-26 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 18:43 Tag for upcoming nolibc pull request Paul E. McKenney
2022-07-26 19:32 ` Willy Tarreau [this message]
2022-07-26 20:27 ` Paul E. McKenney
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=20220726193253.GA16812@1wt.eu \
--to=w@1wt.eu \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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