All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shushkin <edward@namesys.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: David Masover <ninja@slaphack.com>,
	Valdis.Kletnieks@vt.edu, reiserfs-list@namesys.com
Subject: Re: The situation at hand and in the future
Date: Wed, 02 Jun 2004 16:51:43 +0400	[thread overview]
Message-ID: <40BDCD5F.7000706@namesys.com> (raw)
In-Reply-To: <20040602080556.GC4990@nysv.org>

Markus Törnqvist wrote:

>On Tue, Jun 01, 2004 at 05:25:03PM +0400, Edward Shushkin wrote:
>  
>
>>is builtin and can not be changed by users. The user can only assign 
>>plugins. For each
>>kind of transform there is special "none" plugin which means absence of 
>>this transform.
>>    
>>
>
>Is there any chance of this looking more like a crypto/ directory
>than a crypto file?
>  
>
'Looking more' sounds incorrect here (does  directory  look more then 
file? )
You might want special (directory) object plugin. All ideas should be 
implemented
via its methods..

>I really liked David Masover's ideas and I'd like to hear if they
>are somehow infeasible.
>
I am a bit confused: usually I inspire everyone that something is 
feasible ;)

Edward.

>To me they make sense as practical.
>
>Thanks!
>
>  
>

  reply	other threads:[~2004-06-02 12:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 20:01 The situation at hand and in the future mjt
2004-05-27 21:05 ` Valdis.Kletnieks
2004-05-27 22:09   ` David Masover
2004-05-28  6:33     ` mjt
2004-05-28 19:53       ` Valdis.Kletnieks
2004-05-29 12:48         ` mjt
2004-05-29 14:22       ` David Masover
2004-05-29 15:49         ` mjt
2004-05-29 23:16           ` David Masover
2004-05-30  0:41             ` Hubert Chan
2004-05-30 12:29               ` mjt
2004-05-30 16:54                 ` Hubert Chan
2004-05-30 12:27             ` mjt
2004-05-30 17:09               ` Hubert Chan
2004-05-31  0:07                 ` The Amazing Dragon
2004-05-30 17:13               ` Hubert Chan
2004-05-30 18:06                 ` mjt
2004-05-31  0:45               ` David Masover
2004-05-31  8:38                 ` mjt
2004-05-31 15:12                   ` David Masover
2004-05-31 17:20                     ` Hubert Chan
2004-05-31 21:14                       ` David Masover
2004-05-31 15:16                   ` Hubert Chan
2004-06-01 13:25                 ` Edward Shushkin
2004-06-02  8:05                   ` mjt
2004-06-02 12:51                     ` Edward Shushkin [this message]
2004-06-02 15:15                       ` mjt
2004-05-31 18:31             ` Valdis.Kletnieks
2004-05-31 21:15               ` David Masover
2004-06-02  2:45           ` Hans Reiser
2004-05-29 20:04         ` Hubert Chan
2004-05-29 23:19           ` David Masover
2004-05-31 18:27             ` Valdis.Kletnieks
2004-05-31 21:23               ` David Masover
2004-06-01  2:09                 ` Hubert Chan
2004-06-05  4:50                   ` David Masover
2004-06-05  7:30                     ` Valdis.Kletnieks
2004-06-05 10:07                       ` Christian Iversen
2004-06-07 17:35                         ` Valdis.Kletnieks
2004-06-09 22:01                       ` David Masover
2004-06-10  8:23                         ` mjt

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=40BDCD5F.7000706@namesys.com \
    --to=edward@namesys.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=mjt@nysv.org \
    --cc=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.