public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tmpfs sparse file failure in glibc "make check"
Date: Mon, 09 Feb 2004 10:12:43 +0100	[thread overview]
Message-ID: <ovr7xa3awq.fsf@sap.com> (raw)
In-Reply-To: 1jKjY-27v-35@gated-at.bofh.it

Hi Kevin,

On Fri, 30 Jan 2004, Kevin P. Fleming wrote:
> what is the real advantage of both functions being performed by the
> same code?

Less is more? Keep it simple and stupid? You need only one maintainer
and he can additionally work on something different? You do not have
to fix bugs twice? Architectural cleanliness?

Pick (at least) one. I would pick all of them!

Greetings
		Christoph



       reply	other threads:[~2004-02-09  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1jKa4-1TZ-17@gated-at.bofh.it>
     [not found] ` <1jKjY-27v-35@gated-at.bofh.it>
2004-02-09  9:12   ` Christoph Rohland [this message]
2004-01-30  3:35 tmpfs sparse file failure in glibc "make check" Kevin P. Fleming
2004-01-30 16:53 ` Hugh Dickins
2004-01-30 17:07   ` Kevin P. Fleming
2004-01-30 17:47     ` 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=ovr7xa3awq.fsf@sap.com \
    --to=cr@sap.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