From: Jeff Mahoney <jeffm@suse.com>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: 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 19:24:36 -0400 [thread overview]
Message-ID: <480E73B4.8080005@suse.com> (raw)
In-Reply-To: <480E5861.7070205@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Edward Shishkin wrote:
> Jeff Mahoney wrote:
>> 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),
> but s390 seems to be exotic here..
That'll be fine. You don't need to test on all platforms. A ppc64 would
probably be better, but a G3 will work.
> Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.
Sounds good.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIDnOyLPWxlyuTD7IRAsnSAJ4nvWjZQirBhoaz/9kQ/blalomMPgCfTrEU
OIpqVfvIKZYx7kjZm2+lhds=
=8dSb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-04-22 23:24 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 [this message]
2008-04-22 23:28 ` Jake Maciejewski
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=480E73B4.8080005@suse.com \
--to=jeffm@suse.com \
--cc=Vladimir.Saveliev@sun.com \
--cc=edward.shishkin@gmail.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.