From: Christoph Rohland <cr@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: hugh@veritas.com (Hugh Dickins),
andersee@debian.org (Erik Andersen),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [Patch] sysinfo compatibility
Date: 21 Aug 2001 19:30:13 +0200 [thread overview]
Message-ID: <m3y9od1ftm.fsf@linux.local> (raw)
In-Reply-To: <E15ZBvd-0007q8-00@the-village.bc.nu>
Hi Alan,
On Tue, 21 Aug 2001, Alan Cox wrote:
>> before) to make that decision; but concluded it was helping callers
>> who might well go on to add ram+swap, and felt no overriding reason
>> to change that. But you can certainly argue that's inappropriate
>
> There are callers who did add ram + swap
And that's a reason to break compatibility?
Greetings
Christoph
next prev parent reply other threads:[~2001-08-21 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 8:03 [Patch] sysinfo compatibility Christoph Rohland
2001-08-21 10:59 ` Hugh Dickins
2001-08-21 13:50 ` Alan Cox
2001-08-21 17:30 ` Christoph Rohland [this message]
2001-08-21 18:40 ` Alan Cox
2001-08-22 6:40 ` Christoph Rohland
2001-08-21 17:30 ` Christoph Rohland
2001-08-21 17:46 ` Erik Andersen
2001-08-22 6:44 ` Christoph Rohland
2001-08-22 15:45 ` Erik Andersen
2001-08-22 16:04 ` Christoph Rohland
2001-08-21 18:40 ` Hugh Dickins
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=m3y9od1ftm.fsf@linux.local \
--to=cr@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andersee@debian.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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