public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: John Kelly <jak@isp2dial.com>, linux-kernel@vger.kernel.org
Subject: Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
Date: Fri, 12 May 2006 13:50:13 -0600	[thread overview]
Message-ID: <4464E6F5.3000307@wolfmountaingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605121936040.20382@yvahk01.tjqt.qr>

>
>
>>Why drag around old worn out baggage in new kernels?
>>
>>    
>>
If we follow this logic, then.

"LKML == Wikipedia"

"Your contributions can be reverted and removed at any time by any editor."

So why contribute in the first place?

Leave smbfs. The author worked his butt off and contributed to Linux 
with some very useful technology,
and leave his name in contributors.

Jeff





  reply	other threads:[~2006-05-12 19:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605110717.k4B7HuVW006999@shell0.pdx.osdl.net>
2006-05-11 17:51 ` + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree Dave Jones
2006-05-12 15:03   ` Jan Engelhardt
2006-05-12 16:19     ` John Kelly
2006-05-12 16:24       ` Steven Rostedt
2006-05-12 16:31         ` John Kelly
2006-05-12 16:40           ` Tom Rini
2006-05-12 16:48             ` Steven Rostedt
2006-05-12 16:52             ` John Kelly
2006-05-12 16:41           ` Steven Rostedt
2006-05-12 16:59           ` Linus Torvalds
2006-05-12 17:10             ` John Kelly
2006-05-12 17:23               ` Linus Torvalds
2006-05-12 18:13             ` Jeff V. Merkey
2006-05-14  3:11             ` Andrew Morton
2006-05-14  4:37               ` Dave Jones
2006-05-12 17:42           ` Jan Engelhardt
2006-05-12 19:50             ` Jeff V. Merkey [this message]
2006-05-12 16:36       ` grundig
2006-05-15 10:01         ` Helge Hafting
2006-05-11 18:12 ` Jesper Juhl
2006-05-11 18:27   ` Andrew Morton
2006-05-11 18:57     ` John Kelly

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=4464E6F5.3000307@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=jak@isp2dial.com \
    --cc=jengelh@linux01.gwdg.de \
    --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