From: Gary Thomas <gary@mlbassoc.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: ecos-devel@sources.redhat.com
Subject: Re: JFFS2 on eCos
Date: Fri, 26 May 2006 09:55:00 -0000 [thread overview]
Message-ID: <1148637331.20237.15.camel@hermes> (raw)
In-Reply-To: <1148599617.14160.30.camel@shinybook.infradead.org>
On Fri, 2006-05-26 at 00:26 +0100, David Woodhouse wrote:
> Is anyone still interested in JFFS2 on eCos? I've just committed a bunch
> of improvements to mount time and memory usage, and I'm hoping that
> someone will step forward to update and look after the eCos port.
>
> We've abandoned the CVS repository which was used for development of
> JFFS2, and we're doing JFFS2 development in a git tree based on the
> Linux kernel (http://git.infradead.org/?p=mtd-2.6.git)
>
> This means that the eCos code is no longer in CVS right next to the
> Linux version. We used to have a 'mkepk.sh' script which would create an
> epk from what's in CVS -- perhaps we could replace that with a git
> repository which automatically pulls in core JFFS2 changes from the
> Linux tree, but also contains the eCos files. I'm happy enough to give
> accounts to whoever steps forward as JFFS2/eCos maintainers to do
> something like that on git.infradead.org, or give whatever assistance is
> otherwise useful.
Put my head on the block :-) Tell me what needs to be done and how
and I'll make sure it happens.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2006-05-26 9:55 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 [this message]
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
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=1148637331.20237.15.camel@hermes \
--to=gary@mlbassoc.com \
--cc=dwmw2@infradead.org \
--cc=ecos-devel@sources.redhat.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).