From: Stephen Warren <swarren@wwwdotorg.org>
To: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Cc: ARM kernel mailing list <linux-arm-kernel@lists.infradead.org>
Subject: My vacation schedule Apr 17-May 1
Date: Fri, 05 Apr 2013 13:55:24 -0600 [thread overview]
Message-ID: <515F2C2C.5050605@wwwdotorg.org> (raw)
FYI, I'm on vacation/holiday Wed Apr 17th through Wed May 1st. It's
still TBD exactly how much email access I'll have during that time.
Hopefully some, but likely not high volume. I'm
unlikely-to-definitely-won't be doing much in the way of
review/coding/applying patches.
Since this co-incides mostly with the merge window, I don't anticipate
too many problems. Here's hoping:-)
(I'm in two minds whether to spam the main ARM kernel list with this;
hopefully I made the right choice!)
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: My vacation schedule Apr 17-May 1
Date: Fri, 05 Apr 2013 13:55:24 -0600 [thread overview]
Message-ID: <515F2C2C.5050605@wwwdotorg.org> (raw)
FYI, I'm on vacation/holiday Wed Apr 17th through Wed May 1st. It's
still TBD exactly how much email access I'll have during that time.
Hopefully some, but likely not high volume. I'm
unlikely-to-definitely-won't be doing much in the way of
review/coding/applying patches.
Since this co-incides mostly with the merge window, I don't anticipate
too many problems. Here's hoping:-)
(I'm in two minds whether to spam the main ARM kernel list with this;
hopefully I made the right choice!)
next reply other threads:[~2013-04-05 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 19:55 Stephen Warren [this message]
2013-04-05 19:55 ` My vacation schedule Apr 17-May 1 Stephen Warren
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=515F2C2C.5050605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.