From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] doc for 3.18 merge window
Date: Wed, 8 Oct 2014 12:11:44 -0400 [thread overview]
Message-ID: <20141008121144.0f9ac918@tpad.home.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1410070008540.31343@pobox.suse.cz>
On Tue, 7 Oct 2014 00:22:15 +0200 (CEST)
Jiri Kosina <jkosina@suse.cz> wrote:
> I took this over (hopefully temporarily) from Randy who was not willing
> to maintain it any longer.
If you like, perhaps I can take that on for a bit? There is some light
at the end of the tunnel here, and I should be able to do some
interesting things again in the near future...
jon
next prev parent reply other threads:[~2014-10-08 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 22:22 [GIT PULL] doc for 3.18 merge window Jiri Kosina
2014-10-08 16:11 ` Jonathan Corbet [this message]
2014-10-10 11:29 ` Jiri Kosina
2014-10-20 12:45 ` Paul Bolle
2014-10-20 19:08 ` Jiri Kosina
2014-10-21 14:36 ` Jonathan Corbet
2014-10-21 14:45 ` Jonathan Corbet
2014-10-24 14:11 ` Peter Foley
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=20141008121144.0f9ac918@tpad.home.lan \
--to=corbet@lwn.net \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).