From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Clark <dclark@tantalus.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: FW: UBIFS tools and latest 2.6.33 kernel from http://git.infradead.org/users/dedekind/ubifs-v2.6.33.git
Date: Tue, 04 Sep 2012 10:47:33 +0300 [thread overview]
Message-ID: <1346744853.12610.7.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <504448B1.4050205@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Sun, 2012-09-02 at 23:05 -0700, Brian Norris wrote:
> On 09/02/2012 03:57 AM, Artem Bityutskiy wrote:
> > On Fri, 2012-08-31 at 15:18 -0700, Brian Norris wrote:
> >> There was a series of 'writebufsize' fixes that may be missing from
> >> multiple backport trees. I can help you track them down, if you'd like
> >> the help.
> >
> > Sure, go ahead, I can them put them to the backport trees.
>
> OK, I just put up my own github backport tree, with branches for v2.6.32
> through v3.3. I think your v3.4+ repos are fine. URL:
>
> git://github.com/computersforpeace/UBIFS-backports.git
> https://github.com/computersforpeace/UBIFS-backports.git
Thanks Brian, pulled all the branches.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-09-04 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 19:39 FW: UBIFS tools and latest 2.6.33 kernel from http://git.infradead.org/users/dedekind/ubifs-v2.6.33.git David Clark
2012-08-31 12:27 ` Artem Bityutskiy
2012-08-31 22:18 ` Brian Norris
2012-09-02 10:57 ` Artem Bityutskiy
2012-09-03 6:05 ` Brian Norris
2012-09-04 7:47 ` 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=1346744853.12610.7.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dclark@tantalus.com \
--cc=linux-mtd@lists.infradead.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.