From: Ferenc Havasi <havasi@inf.u-szeged.hu>
To: linux-mtd@lists.infradead.org
Cc: Steven Scholz <steven.scholz@imc-berlin.de>
Subject: Re: SUMMARY for JFFS2?
Date: Thu, 03 Mar 2005 12:58:03 +0100 [thread overview]
Message-ID: <4226FBCB.5020007@inf.u-szeged.hu> (raw)
In-Reply-To: <42232855.3020408@imc-berlin.de>
Steven Scholz wrote:
> IIUC then the SUMMARY stuff goes into JFFS3.
> But are there any plans to officially include it into the JFFS2 code?
>
> It's quite cumbersome to update MTD CVS and then merge the patch
> http://www.inf.u-szeged.hu/jffs2/jffs2-summary-20050211.patch by hand.
>
> Since its a compile time option is there anything speaking against such
> inclusion?
If David (dwmw2) says yes, we are ready to commit. Due to Steven's and
some other people testing I think now it is stable.
Regards,
Ferenc
next prev parent reply other threads:[~2005-03-03 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 14:19 SUMMARY for JFFS2? Steven Scholz
2005-03-03 11:58 ` Ferenc Havasi [this message]
2005-04-14 9:15 ` Steven Scholz
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=4226FBCB.5020007@inf.u-szeged.hu \
--to=havasi@inf.u-szeged.hu \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.de \
/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