From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [Announce] Upcoming Time Off
Date: Mon, 14 Aug 2017 11:06:41 -0400 [thread overview]
Message-ID: <cc358422-24ea-045a-ac72-ec8e0a258076@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1645 bytes --]
I need to make everyone aware of some upcoming PTO I have scheduled as
it will impact the timing of this merge window's for-next branch inclusions.
My family and I are moving into a new home at the end of this month. As
my wife is a public school teacher, she can't really take time off for
moving, but I can, so I have. I'm scheduled to start my PTO on August
30th, so that means there are only 12 working days left between now and
when I start my PTO.
As is typical for me, I will likely check my email as I can even while
on PTO. However, what's not typical, is that I will be moving my entire
home network and switching Internet providers. That little wrinkle
means I may be entirely offline for longer than I would like. I will
prepare for the worst by having my for-next branch ready to go and and
pull requests submitted to Linus prior to shutting down my network (the
merge window might already be open by the time I shut down, or it might
not, but regardless, I'll have my pull request in either way).
Fortunately, the merge window and the first -rc will be happening while
I'm down for the most part.
I am not scheduled to return back to work until Sept. 18th. We might be
as far in as -rc2 by then. I'll notify Linus of this ahead of time, and
I'll prioritize processing of backlogged -rc items once I return.
Thanks for your understanding as I do all the stuff that needs to be
done when we move into the house.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG Key ID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next reply other threads:[~2017-08-14 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 15:06 Doug Ledford [this message]
[not found] ` <cc358422-24ea-045a-ac72-ec8e0a258076-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-14 16:17 ` [Announce] Upcoming Time Off Christopher Lameter
2017-09-18 20:36 ` Doug Ledford
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=cc358422-24ea-045a-ac72-ec8e0a258076@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).