From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] UBI changes for 3.12-rc1
Date: Mon, 16 Sep 2013 11:01:53 +0300 [thread overview]
Message-ID: <1379318513.17490.64.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1379316610.17490.58.camel@sauron.fi.intel.com>
On Mon, 2013-09-16 at 10:30 +0300, Artem Bityutskiy wrote:
> Hi Linus,
>
> very few changes. I'll start using a single UBI/UBIFS tree instead
> of 2 trees from now on. So in the future you'll get 1 small pull
> request instead of 2 tiny ones.
Also, I do realize this is very late, apologies for this. But the
changes are just small fixes so I they should be OK for -rc2 as well.
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2013-09-16 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 7:30 [GIT PULL] UBI changes for 3.12-rc1 Artem Bityutskiy
2013-09-16 8:01 ` Artem Bityutskiy [this message]
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=1379318513.17490.64.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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