From: Gary Thomas <gary@mlbassoc.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: ecos-devel@sources.redhat.com, Chi Xiaobo <xbchi@utstar.com>,
jifl@ecoscentric.com
Subject: Re: JFFS2 on eCos
Date: Wed, 21 Jun 2006 13:25:00 -0000 [thread overview]
Message-ID: <1150896325.16508.81.camel@hermes> (raw)
In-Reply-To: <1150896069.3176.673.camel@pmac.infradead.org>
On Wed, 2006-06-21 at 14:21 +0100, David Woodhouse wrote:
> On Mon, 2006-05-29 at 15:32 +0100, David Woodhouse wrote:
> > I've created git://git.infradead.org/~dwmw2/jffs2-ecos-core.git which
> > contains just the JFFS2 files, moved into a 'src/' directory. It
> > preserves the full revision history of those files from the kernel, and
> > it's automatically updated from the kernel tree every night. It's
> > browsable at http://git.infradead.org/?p=users/dwmw2/jffs2-ecos-core.git
> >
> > The script which does it, if you're interested, is at
> > http://david.woodhou.se/extract-jffs2-git.sh -- we can redo the whole
> > thing with a different set of $JFFS2FILES if you want.
> >
> > I've also created another tree which derives from the above, and added
> > the eCos-specific files to it. That one is 'jffs2-ecos.git' in the same
> > directory.
> >
> > The idea is that you can merge changes (with 'git pull') from the
> > 'jffs2-ecos-core' tree into the working 'jffs2-ecos' tree.
> >
> > I haven't based the jffs2-ecos tree on the _current_ state of the
> > exported jffs2-ecos-core; it's based on a version from November last
> > year, which corresponds to the Andrew's last update to the eCos code in
> > my tree -- this means that we have some expectation that it might
> > actually build and work in eCos.
> >
> > It's probably work making sure that _does_ actually work before starting
> > to pull in further changes from the upstream JFFS2 codebase.
>
> Any progress on this?
I'm trying :-) However, other stuff keeps getting in the way.
I'll do my best to move it up the heap...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2006-06-21 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 23:27 David Woodhouse
2006-05-26 9:55 ` Gary Thomas
2006-05-26 13:02 ` David Woodhouse
2006-05-29 14:32 ` David Woodhouse
2006-05-29 17:29 ` David Woodhouse
2006-06-21 13:21 ` David Woodhouse
2006-06-21 13:25 ` Gary Thomas [this message]
2006-05-29 2:15 答复: " Chi Xiaobo
2006-05-29 14:41 ` David Woodhouse
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=1150896325.16508.81.camel@hermes \
--to=gary@mlbassoc.com \
--cc=dwmw2@infradead.org \
--cc=ecos-devel@sources.redhat.com \
--cc=jifl@ecoscentric.com \
--cc=xbchi@utstar.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).