linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: per.persson@gnosjo.pp.se (Per Persson)
Cc: marcelo@conectiva.com.br, alan@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: triple_down et al.
Date: Mon, 27 Jan 2003 09:49:20 -0500 (EST)	[thread overview]
Message-ID: <200301271449.h0REnLl09461@devserv.devel.redhat.com> (raw)
In-Reply-To: <002e01c2c3e8$e32a89c0$0e02a8c0@solveig> from "Per Persson" at Jan 24, 2003 09:40:42 PM

> Here's a patch I tried to get into the 2.4 series in autumn 2001. I was
> however told that it was too close to the start of the 2.5 series.
> 
> The patch cleans up the "messy" triple_down code in fs.h.

Is this aimed at 2.4 or 2.5 ?

  reply	other threads:[~2003-01-27 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 20:40 triple_down et al Per Persson
2003-01-27 14:49 ` Alan Cox [this message]
2003-02-02  0:03   ` Matthew Wilcox

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=200301271449.h0REnLl09461@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=per.persson@gnosjo.pp.se \
    /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;
as well as URLs for NNTP newsgroup(s).