All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Domenico Andreoli <cavok@tiscali.it>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 can't fix 1 fixable corruption
Date: Fri, 23 Apr 2004 17:00:44 -0700	[thread overview]
Message-ID: <4089AE2C.5010200@namesys.com> (raw)
In-Reply-To: <200404240048.40469.vitaly@namesys.com>

Vitaly Fertman wrote:

>On Saturday 24 April 2004 00:19, Hans Reiser wrote:
>  
>
>>Vitaly Fertman wrote:
>>    
>>
>>>On Thursday 22 April 2004 15:44, Domenico Andreoli wrote:
>>>      
>>>
>>>>On Thu, Apr 22, 2004 at 02:46:21PM +0400, Vitaly Fertman wrote:
>>>>        
>>>>
>>>>>with --enable-stand-alone you get another 'stand alone' library that
>>>>>includes the minimum of the code needed for programs like grub --
>>>>>no librepair, no tree balancing code, no modification code, etc. The
>>>>>code is minimised to be used with grub stage1_5. Libaal in stand-alone
>>>>>includes simple memory menagement methods (malloc, free) to avoid
>>>>>linking to libc -- as it links to no other libraries it is called
>>>>>stand-alone.
>>>>>          
>>>>>
>>>>thanks, now it's much more clear :)
>>>>        
>>>>
>>how about calling it --minimal-footprint and fixing the documentation to
>>include some of the words above?
>>    
>>
>
>It have to be --enable-minimal-footprint as you get this minimal-footprint 
>library in addition to the base library.
>  
>
I don't understand what you said.

>  
>
>>Please work on reviewing your documentation and options naming for
>>greater clarity for a day.
>>    
>>
>
>yes, I am going to review all documentation just after finishing with 
>the plugin inheritance.
>
>  
>


  reply	other threads:[~2004-04-24  0:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 14:33 fsck.reiser4 can't fix 1 fixable corruption Raymond A. Meijer
2004-04-20 18:54 ` Sander Sweers
2004-04-21  8:09   ` Raymond A. Meijer
2004-04-21  8:55 ` Vitaly Fertman
2004-04-21  9:11   ` Raymond A. Meijer
2004-04-21  9:59   ` Raymond A. Meijer
2004-04-21 11:51     ` Vitaly Fertman
2004-04-21 12:05       ` Carl-Daniel Hailfinger
2004-04-21 12:09       ` Raymond A. Meijer
2004-04-21 12:19         ` Sander Sweers
2004-04-21 19:30           ` Sander Sweers
2004-04-21 19:44             ` Domenico Andreoli
2004-04-21 20:13               ` Sander Sweers
2004-04-21 20:53                 ` Domenico Andreoli
2004-04-21 21:13                   ` Vitaly Fertman
2004-04-21 21:58                     ` Domenico Andreoli
2004-04-22 10:46                       ` Vitaly Fertman
2004-04-22 11:44                         ` Domenico Andreoli
2004-04-23  9:15                           ` Vitaly Fertman
2004-04-23 20:19                             ` Hans Reiser
2004-04-23 20:59                               ` Vitaly Fertman
2004-04-24  0:00                                 ` Hans Reiser [this message]
2004-04-22 12:37                         ` Domenico Andreoli
2004-04-22 17:51                           ` Hans Reiser
2004-04-22 18:30               ` Hans Reiser
2004-04-23  1:22                 ` Domenico Andreoli
2004-04-25 16:31                   ` Hans Reiser
2004-04-25 20:31                     ` Domenico Andreoli
2004-04-30  3:16                       ` Hans Reiser
2004-04-30 10:18                         ` Vitaly Fertman
2004-04-28  9:09                     ` Vitaly Fertman
2004-04-23  7:04                 ` Yury Umanets
2004-04-23  9:03                   ` Vitaly Fertman
2004-04-23 10:27                     ` Domenico Andreoli
2004-04-23 12:54                       ` Vitaly Fertman
2004-04-23 11:01                     ` Yury Umanets
2004-04-21 13:30       ` reiser4progs 0.5.4 build error (was Re: fsck.reiser4 can't fix 1 fixable corruption) Domenico Andreoli

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=4089AE2C.5010200@namesys.com \
    --to=reiser@namesys.com \
    --cc=cavok@tiscali.it \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@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.