public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Tom Rini <trini@kernel.crashing.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: reiserfs-list <reiserfs-list@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] Re: Linux 2.4.12-ac1
Date: Fri, 12 Oct 2001 13:18:44 -0400	[thread overview]
Message-ID: <1822570000.1002907124@tiny> (raw)
In-Reply-To: <20011012083616.C9992@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20011012072910.N21564@cpe-24-221-152-185.az.sprintbbd.net> <E15s44B-0007Vk-00@the-village.bc.nu> <20011012083616.C9992@cpe-24-221-152-185.az.sprintbbd.net>



On Friday, October 12, 2001 08:36:16 AM -0700 Tom Rini <trini@kernel.crashing.org> wrote:

> On Fri, Oct 12, 2001 at 04:17:39PM +0100, Alan Cox wrote:
>> > On Fri, Oct 12, 2001 at 02:17:26PM +0100, Alan Cox wrote:
>> > 
>> > > 2.4.12-ac1
>> > > o	Merge the majority of 2.4.11/12
>> > > 	-	Fall back to the Linus reiserfs code set
>> > [snip]
>> > 
>> > The endian-safe patches will come back tho, right?  I don't think those
>> > have made it into Linus' tree yet...
>> 
>> Really what needs to happen is the important bits that were tested and
>> the reiser folks were happy with get pushed back bit by bit into both trees
>> now
> [reiserfs list added to cc]
> 
> That would be nice.  Are there any plans on behalf of the reiserfs
> people to merge in the Endian-Safeness patches now?

Jeff had sent them to linus before 2.4.10 came out, and again 
earlier this week.  Hopefully they'll make it into 2.4.13pre.

-chris


  parent reply	other threads:[~2001-10-12 17:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 13:17 Linux 2.4.12-ac1 Alan Cox
2001-10-12 14:04 ` Udo A. Steinberg
2001-10-12 18:06   ` Rui Sousa
2001-10-12 18:13     ` Udo A. Steinberg
2001-10-12 19:22       ` Rui Sousa
2001-10-12 19:40         ` Udo A. Steinberg
2001-10-12 14:29 ` Tom Rini
2001-10-12 15:17   ` Alan Cox
2001-10-12 15:36     ` Tom Rini
2001-10-12 15:47       ` Tom Gall
2001-10-12 20:30         ` [reiserfs-list] " Hans Reiser
2001-10-12 15:55       ` (memory?) bug between 2.4.9-ac10 and -ac14 Mikael Johansson
2001-10-12 17:18       ` Chris Mason [this message]
2001-10-12 21:26 ` Linux 2.4.12-ac1 J . A . Magallon
2001-10-12 21:52   ` Rik van Riel
2001-10-12 22:04     ` J . A . Magallon
2001-10-12 23:24 ` Thomas Davis
2001-10-13  4:06 ` Tom Vier
2001-10-14  1:34 ` Tom Rini
2001-10-14  1:34 ` Tom Rini

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=1822570000.1002907124@tiny \
    --to=mason@suse.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=trini@kernel.crashing.org \
    /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