linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: RFC:  what's in a stable series?
Date: 10 Jul 2003 13:42:00 +0100	[thread overview]
Message-ID: <1057840919.8027.19.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307100910550.7857@freak.distro.conectiva>

On Iau, 2003-07-10 at 13:13, Marcelo Tosatti wrote:
> So Christoph's quota patch does not support vendors "v1" files?
> 
> I must be misunderstanding someone.

There are three species of quota in Linux

v0	(official old Linux)
v1	(most 2.4 vendor trees)
v2	(the 2.5 format)

[Plus other per file system stuff that is abstracted by the quota
updates and used by folks like XFS]

The v1 quota definitely doesn't belong in 2.5, but its needed by a
lot of 2.4 users who come from vendor trees (and may want to go back
again)



  reply	other threads:[~2003-07-10 12:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  1:06 RFC: what's in a stable series? Jeff Garzik
2003-07-10  1:08 ` Jeff Garzik
2003-07-10  3:34 ` Herbert Pötzl
2003-07-10  7:53   ` Christoph Hellwig
2003-07-10 11:22   ` Alan Cox
2003-07-10 12:36     ` Herbert Pötzl
2003-07-10  3:54 ` Greg KH
2003-07-10  3:54 ` Marcelo Tosatti
2003-07-10  4:16   ` Andrew Morton
2003-07-10  7:53     ` Christoph Hellwig
2003-07-10  8:25       ` Andrew Morton
2003-07-10  7:53   ` Christoph Hellwig
2003-07-10 11:19     ` Alan Cox
2003-07-10 12:13       ` Marcelo Tosatti
2003-07-10 12:42         ` Alan Cox [this message]
2003-07-10 15:15           ` Christoph Hellwig
2003-07-10 19:00             ` Jan Kara
2003-07-11  8:36               ` Christoph Hellwig
2003-07-11  9:21             ` Alan Cox
2003-07-10 15:12         ` Christoph Hellwig
2003-07-10 15:11       ` Christoph Hellwig

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=1057840919.8027.19.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@digeo.com \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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).