public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] new quota code
Date: Mon, 07 Jul 2003 19:02:42 -0400	[thread overview]
Message-ID: <3F09FC12.4070609@pobox.com> (raw)
In-Reply-To: <200307072105.h67L50ir024592@hera.kernel.org>

Linux Kernel Mailing List wrote:
> ChangeSet 1.1059, 2003/07/07 17:01:15-03:00, hch@lst.de
> 
> 	[PATCH] new quota code
> 	
> 	Okay, here's the quota patch.  Basically all changes are from Jan Kara
> 	and I backport them from 2.5.  The 32bit quota code has been shipped
> 	by the commercial vendors ever since they used Linux 2.4 and this
> 	particular codebase with backwards compatiblity support is around
> 	in the 2.5, the XFS tree, -ac and -aa for a long time.  The only
> 	change over that version is that support for the old 16bit quota
> 	format and the old quotactl ABI is enabled unconditionally, i.e.
> 	there's no way to render your system unusable by wrong make config
> 	choices [1].
> 	
> 	[1] This also mean completely dropping support for the interim ABI
> 	used in the early 32bit quota patches as it's mutally incompatible
> 	to the old ABI.  But we never ever shipped that in any mainline kernels
> 	so there's no problem.


"no problem" being defined here as "multiple vendors shipped it but I 
don't care", right?

Why do we need a third (fourth?) 2.4 quota abi/api floating around?

	Jeff




       reply	other threads:[~2003-07-07 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200307072105.h67L50ir024592@hera.kernel.org>
2003-07-07 23:02 ` Jeff Garzik [this message]
2003-07-08  6:21   ` [PATCH] new quota code 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=3F09FC12.4070609@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=hch@infradead.org \
    --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