linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Daniel Aragonés" <danarag@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] minix filesystem: Corrected patch
Date: Sun, 22 Jan 2006 22:37:19 +0200	[thread overview]
Message-ID: <1137962239.8704.4.camel@localhost> (raw)
In-Reply-To: <43D3E96C.2050703@gmail.com>

Hi Daniel,

On Sun, 2006-01-22 at 21:22 +0100, Daniel Aragonés wrote:
> Yes, but if I do, is closer to a rewrite of the preexistent code. And
> I think that it not deserves it. Minix is not so important (sorry if
> some one is listening).

Then what's the point of merging your patch to the mainline? We want
clean maintainable code in the kernel so I hope you reconsider
addressing my comments. Thanks.

			Pekka


  reply	other threads:[~2006-01-22 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 20:22 [PATCH/RFC] minix filesystem: Corrected patch Daniel Aragonés
2006-01-22 20:37 ` Pekka Enberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-22 18:34 Daniel Aragonés
2006-01-22 19:17 ` Pekka Enberg

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=1137962239.8704.4.camel@localhost \
    --to=penberg@cs.helsinki.fi \
    --cc=danarag@gmail.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;
as well as URLs for NNTP newsgroup(s).