From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: l2-mtd-2.6.git to linux-next
Date: Tue, 07 Jun 2011 07:40:15 +0300 [thread overview]
Message-ID: <1307421615.11104.14.camel@localhost> (raw)
In-Reply-To: <1307345850.3135.24.camel@localhost>
David,
On Mon, 2011-06-06 at 10:37 +0300, Artem Bityutskiy wrote:
> Stephen,
>
> as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:
>
> git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master
although you already asked about this, sfr wanted your deliberate ack.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-06-07 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 7:37 l2-mtd-2.6.git to linux-next Artem Bityutskiy
2011-06-07 4:40 ` Artem Bityutskiy [this message]
2011-06-07 10:55 ` David Woodhouse
2011-06-08 0:31 ` Stephen Rothwell
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=1307421615.11104.14.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).