public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Segin <segin2005@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Minix 3 filesystem support
Date: Mon, 9 Jan 2006 06:29:35 +0000	[thread overview]
Message-ID: <20060109062935.GH27946@ftp.linux.org.uk> (raw)
In-Reply-To: <43C1CE74.4000302@gmail.com>

On Sun, Jan 08, 2006 at 09:46:12PM -0500, Segin wrote:
> The attached email contains diffs for making the Minix version 3 
> filesystem work with Linux.
> 
> Please note that I do not subscribe to the mailing list.
> 
> Also, please send all replies about this patch which would normally be 
> emailed to me to the newsgroup comp.os.minix. I did not write this 
> patch, I am just making it available to the Linux kernel mailing list.

If/when author decides that patch is ready for review and asks for
comments, he will be perfectly able to post the thing himself.
As it is, you've just posted something that might be a beginning
of such patch; WTF are we supposed to do with it?  Dump unsolicited
comments on its author?  Bypass him completely and use that chunk
to implement the entire thing?  Oh, wait - take discussion of
Linux kernel internals to comp.os.minix.  _That's_ the ticket.

If the patch author has any questions, he's more than welcome here, on
fsdevel or any appropriate newsgroup or IRC channel.

This is not a slashdot.  Posting an equivalent of "k3wl l1nk" will earn
you nothing but a swift kick in the place where your head is, quite
possibly followed by more elaborate treatment from patch author who has
every right to be thoroughly pissed off at you.

      reply	other threads:[~2006-01-09  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09  2:46 Minix 3 filesystem support Segin
2006-01-09  6:29 ` Al Viro [this message]

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=20060109062935.GH27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=segin2005@gmail.com \
    /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