From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gregory Maxwell <gmaxwell@gmail.com>
Subject: Re: reiser4progs do not handle the reiser4 format changes
Date: Thu, 21 Jul 2005 04:10:55 -0400
Message-ID: <e692861c0507210110777588d6@mail.gmail.com>
References: <42DE5A5E.9020404@namesys.com> <42DE9DD6.1090104@slaphack.com>
	 <42DEF3C7.3040104@namesys.com>
Reply-To: Gregory Maxwell <gmaxwell@gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Return-path: <reiserfs-list-return-25224-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <42DEF3C7.3040104@namesys.com>
Content-Disposition: inline
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Edward Shishkin <edward@namesys.com>
Cc: David Masover <ninja@slaphack.com>, "E.Gryaznova" <grev@namesys.com>, reiserfs-list@namesys.com

On 7/20/05, Edward Shishkin <edward@namesys.com> wrote:
> like other existing
> ones. This will be a way to create cryptcompress files per superblock.
> There is another
> more flexible way (which is compatible with the previous one) to create
> it per file/directory,
> but it uses deprecated metas interface..

Per ... superblock?
Excuse me?

Nonselective use of this feature will be nearly useless. There must be
an API to selectively control the feature.

This sounds like a silly tantrum about the interface changes.