From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org, jakub.kicinski@netronome.com
Cc: linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Taking a day off...
Date: Mon, 12 Aug 2019 21:26:59 -0700 (PDT) [thread overview]
Message-ID: <20190812.212659.1072592048193337024.davem@davemloft.net> (raw)
Hello everyone,
Tomorrow I will be letting Jakub Kicinski manage the net and net-next
GIT trees. So he will be integrating patches into GIT and doing git
pulls from people. He will alway keep the patchwork states up to
date, just like I do.
I completely expect everyone to give Jakub the same respect and
consideration they usually give to me, because he deserves it.
In the future, when I need to take a few days off, I will hand things
over to Jakub in a similar way.
Thank you.
reply other threads:[~2019-08-13 4:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190812.212659.1072592048193337024.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bpf@vger.kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.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).