All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Yury Umanets <umka@namesys.com>,
	reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 snapshot for August 26th.
Date: Wed, 27 Aug 2003 19:54:08 +0400	[thread overview]
Message-ID: <3F4CD420.4000603@namesys.com> (raw)
In-Reply-To: <1061983191.678.1.camel@teapot.felipe-alfaro.com>

Felipe Alfaro Solana wrote:

>On Wed, 2003-08-27 at 08:03, Yury Umanets wrote:
>  
>
>>> 
>>>Information: Reiser4 is going to be created on /dev/sda5.
>>>(Yes/No): Yes
>>>Creating reiser4 on /dev/sda5...
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
>>>mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
>>>done
>>>Synchronizing /dev/sda5...done
>>>      
>>>
>>I will fix it soon.
>>    
>>
>
>Will Reiser4 be integrated into 2.6.0-test kernels anytime soon?
>This would reduce time between releases and would open up it to a wider
>audience for testing
>
>
>
>  
>
This is not a Namesys decision, I encourage you to ask Linus and Andrew 
about it though.  I would like to see it go in as an experimental marked 
filesystem....

-- 
Hans



  reply	other threads:[~2003-08-27 15:54 UTC|newest]

Thread overview: 37+ 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
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-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 [this message]
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=3F4CD420.4000603@namesys.com \
    --to=reiser@namesys.com \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=umka@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.