All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jake Maciejewski <maciejej@msoe.edu>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
	Vladimir Saveliev <Vladimir.Saveliev@sun.com>,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>,
	Ric Wheeler <ric@emc.com>
Subject: Re: Forked reiserfsprogs
Date: Tue, 22 Apr 2008 18:28:29 -0500	[thread overview]
Message-ID: <1208906909.26981.6.camel@localhost> (raw)
In-Reply-To: <480E5861.7070205@gmail.com>

On Wed, 2008-04-23 at 01:28 +0400, Edward Shishkin wrote:
> Jeff Mahoney wrote:
> 
> > Edward Shishkin wrote:
> 
> [...]
> 
> > >Problems:
> >
> > >1. The status of Reiserfsprogs-3.6.20.1 should be clarified.
> > >  Did the Vladimir's branch get testing?
> >
> >
> > I believe this is the version I was working with. It got testing, and
> > the results weren't good. I'm not sure if these are specific to
> > Vladimir's version or to Vitaly's version,
> 
> 
> I think it was Vitaly's one (3.6.20), as Vladimir told about monthly
> snapshots somewhere in ./tmp..
> 
> > but when I pushed it for a
> > SLE10 SP2 alpha, I ended up getting lots of bug reports. They focused
> > mainly in the area of endianness and divide-by-zero errors. So, I
> > wouldn't call this version stable at all.
> 
> 
> Hum.. I didn't know about it. It seems we need to rename it to something
> like 3.6.20-preX..
> 
> > I didn't have the time or
> > interest to figure out what these problems were especially since, at the
> > time, I was told a real 3.6.20 didn't actually exist. I ended up backing
> > out the change and porting all my patches to what you're calling 3.6.19.1.
> >
> > >2. I don't have Reiserfsprogs-3.6.20.1. Are there any snapshot
> > >  on this mirror that can be put for public needs:
> > >  ftp://ftp.icm.edu.pl/packages/linux-reiserfs ?
> > >3. Perhaps, I will need help in addressing possible bugreports
> > >  and the final merge of all branches.
> >
> > >Any comments, updates, suggestions?
> >
> >
> > If we actually have a stable 3.6.20, I'd be happy to forward port my
> > patches. One thing needs to happen, though: We absolutely need to start
> > testing on big endian hardware. We ship reiserfs on both powerpc and
> > s390, and hit the endian bugs quickly on those systems.
> >
> 
> Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for 
> reiser4),

You could also try PearPC. On a fast x86/amd64 machine it probably isn't
any slower than a low-spec G3.

I have a beige G3 I'm not doing anything with (aside from testing
reiser4 on it some time ago), but getting it to boot Linux without MacOS
8/9 installed is borderline voodoo, so I assume you wouldn't be
interested.

> but s390 seems to be exotic here..
> 
> Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.
> 
> Thanks Jeff.
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Jake Maciejewski <maciejej@msoe.edu>


  parent reply	other threads:[~2008-04-22 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 19:22 Forked reiserfsprogs Edward Shishkin
2008-04-21  3:16 ` Jeff Mahoney
2008-04-22 21:28   ` Edward Shishkin
2008-04-22 23:24     ` Jeff Mahoney
2008-04-22 23:28     ` Jake Maciejewski [this message]
2008-04-25 18:45       ` Edward Shishkin
2008-04-27  6:30         ` Jake Maciejewski

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=1208906909.26981.6.camel@localhost \
    --to=maciejej@msoe.edu \
    --cc=Vladimir.Saveliev@sun.com \
    --cc=edward.shishkin@gmail.com \
    --cc=jeffm@suse.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=ric@emc.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.