public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: Oleg Drokin <green@namesys.com>,
	reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
	linux-kernel@vger.kernel.org
Subject: Re: reiser4 snapshot for August 26th.
Date: Tue, 26 Aug 2003 23:22:05 +0400	[thread overview]
Message-ID: <3F4BB35D.6030705@namesys.com> (raw)
In-Reply-To: <1061923101.1670.9.camel@spc9.esa.lanl.gov>

Steven Cole wrote:

>On Tue, 2003-08-26 at 12:20, Steven Cole wrote:
>  
>
>>On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
>>    
>>
>>>Hello!
>>>
>>>   I have just released another reiser4 snapshot that I hope all interested
>>>   parties will try. It is released against 2.6.0-test4.
>>>   You can find it at http://namesys.com/snapshots/2003.08.26
>>>   I include release notes below.
>>>
>>>Reiser4 snapshot for 2003.08.26
>>>
>>>      
>>>
>>I got this error while attempting to compile with reiser4.
>>Snippet from .config follows.
>>
>>Steven
>>
>>  CC      fs/reiser4/plugin/file/tail_conversion.o
>>  CC      fs/reiser4/sys_reiser4.o
>>fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
>>    
>>
>[snipped]
>  
>
>>[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
>>CONFIG_REISER4_FS=y
>>CONFIG_REISER4_FS_SYSCALL=y
>>    
>>
>
>I should have read this more carefully :(
>
>config REISER4_FS_SYSCALL
>        bool "Enable reiser4 system call"
>        depends on REISER4_FS
>        default n
>        ---help---
>      Adds sys_reiser4() syscall.
>      This code is not in good shape yet and may not compile and stuff like that.
>
>Without REISER4_FS_SYSCALL, -test4 with reiser4 compiles fine.  Sorry about the noise.
>
>Steven
>
>
>
>
>  
>
Users should not be expected to read help text in a case like this.If it 
does not compile, it should not be visible.

-- 
Hans



  reply	other threads:[~2003-08-26 19:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 10:22 reiser4 snapshot for August 26th Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26   ` Alex Zarochentsev
2003-08-26 19:36     ` Felipe Alfaro Solana
2003-08-26 19:43       ` Oleg Drokin
2003-08-26 19:51         ` Steven Cole
2003-08-26 20:05           ` Mike Fedyk
2003-08-26 20:13             ` Steven Cole
2003-08-26 20:26               ` Mike Fedyk
2003-08-26 20:25                 ` Steven Cole
2003-08-26 20:30                 ` Hans Reiser
2003-08-26 20:28           ` Hans Reiser
2003-08-26 19:53         ` Mike Fedyk
2003-08-26 19:57       ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-26 22:20         ` Resident Boxholder
2003-08-27 10:35         ` Oleg Drokin
2003-08-28  7:28           ` Resident Boxholder
2003-08-26 18:38   ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22     ` Hans Reiser [this message]
2003-08-26 18:38   ` Oleg Drokin
2003-08-26 18:41   ` Hans Reiser
2003-08-26 18:41     ` Alex Zarochentsev
2003-08-26 19:14       ` Steven Cole
2003-08-28 11:46         ` Alex Zarochentsev
2003-08-28 15:12           ` Steven Cole
2003-08-28 16:33           ` Tupshin Harper
2003-08-26 19:15       ` Hans Reiser
2003-08-28 18:31   ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27  7:38   ` Oleg Drokin
2003-08-27  5:52 ` Ian Wienand
2003-08-27  6:03   ` Yury Umanets
2003-08-27 11:19     ` Felipe Alfaro Solana
2003-08-27 15:54       ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52   ` Nikita Danilov

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=3F4BB35D.6030705@namesys.com \
    --to=reiser@namesys.com \
    --cc=elenstev@mesatop.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox