public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Hans Reiser <reiser@namesys.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: ReiserFS Bug Fixes 2 of 6
Date: 07 Apr 2002 13:18:36 -0400	[thread overview]
Message-ID: <1018199916.3563.275.camel@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0204061107230.632-100000@weyl.math.psu.edu>

On Sat, 2002-04-06 at 11:07, Alexander Viro wrote:
> 
> 
> On Sat, 6 Apr 2002, Hans Reiser wrote:
> 
> > 
> > This changeset is to fix reiserfs problems that arose after applying one of
> > Al Viro's cleanup. This changeset simply removes offending part.
> 
> Hans, it's already fixed by Oleg's patch.
> 

Correct.  Hans, numerous people have explained that reversing this patch
fixes nothing.  

-chris



      parent reply	other threads:[~2002-04-07 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 20:25 ReiserFS Bug Fixes 2 of 6 Hans Reiser
2002-04-06 16:07 ` Alexander Viro
2002-04-06 16:17   ` 2.4.x kernels vs. IDT halfdead
2002-04-07 17:18   ` Chris Mason [this message]

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=1018199916.3563.275.camel@tiny \
    --to=mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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