public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: lorenzo@gun.org, linux-mtd@lists.infradead.org
Subject: Re: xattr support  for JFFS3
Date: Fri, 25 Feb 2005 15:08:58 +0100	[thread overview]
Message-ID: <1109340538.18747.15.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0502250919100.5525@phoenix.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

El vie, 25-02-2005 a las 09:19 +0000, Artem B. Bityuckiy escribió:
> I offer to keep you work public as the community might assist you. 
> Furthermore, you probably may use the existing JFFS3 design document and 
> to add your xattr design there.

That's what we are going to do, the development is going on JFFS3, and
of course I've read the specifications and design of JFFS2 at RH's JFFS2
site (thanks to David for pointing this out).

Thanks for the comments,
Cheers. 
-- 
Lorenzo Hernández García-Hierro <lorenzo@gnu.org> 
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-02-25 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 23:31 xattr support for JFFS3 Keshavamurthy, Anil S
2005-02-24  0:58 ` Josh Boyer
2005-02-24  1:15   ` Keshavamurthy Anil S
2005-02-24 15:42     ` Lorenzo Hernández García-Hierro
2005-02-24 23:56       ` Keshavamurthy Anil S
2005-02-25  9:19         ` Artem B. Bityuckiy
2005-02-25 14:08           ` Lorenzo Hernández García-Hierro [this message]
2005-02-25  9:51         ` Thomas Gleixner
2005-02-25 14:12           ` Lorenzo Hernández García-Hierro
2005-02-25 14:07         ` Lorenzo Hernández García-Hierro
2005-02-24 10:32 ` Artem B. Bityuckiy

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=1109340538.18747.15.camel@localhost.localdomain \
    --to=lorenzo@gnu.org \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lorenzo@gun.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