From: Adrian Bunk <bunk@stusta.de>
To: Steven French <sfrench@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, samba@samba.org,
Urban.Widmark@enlight.net
Subject: Re: New maintainer needed for the Linux smb filesystem
Date: Mon, 22 Aug 2005 03:49:57 +0200 [thread overview]
Message-ID: <20050822014956.GI5726@stusta.de> (raw)
In-Reply-To: <OF200CE886.6A353FBA-ON87257065.0005812F-86257065.0005B594@us.ibm.com>
On Sun, Aug 21, 2005 at 08:01:57PM -0500, Steven French wrote:
>...
> I don't mind fixing any major smbfs bugs that are found as needed, the code
> is not hard to follow, but I would rather focus on the three current cifs
> priorities:
>...
It sounds as if you would be a great choice as new smbfs maintainer -
you know both the protocols involved and the Linux kernel.
Noone expects big feature additions to the smbfs code, maintainership
consists of:
- reviewing patches
- handling bugs (the 16 open bugs in the kernel Bugzilla give a rough
impression of what problems people face)
cifs might be the future, but until it supports a superset of smbfs
users require smbfs - and a good smbfs makes their life easier.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-22 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 14:34 Adrian Bunk
2005-08-21 19:46 ` Andrew Morton
2005-08-22 1:06 ` Dave Jones
[not found] ` <OF200CE886.6A353FBA-ON87257065.0005812F-86257065.0005B594@us.ibm.com>
2005-08-22 1:49 ` Adrian Bunk [this message]
2005-08-22 3:09 ` [Samba] " Gerald (Jerry) Carter
2005-08-23 1:11 ` Ian Kent
2005-08-23 15:08 ` Gerald (Jerry) Carter
2005-08-24 0:47 ` Ian Kent
[not found] <20050821143457.GA5726@stusta.de.suse.lists.linux.kernel>
2005-08-21 20:26 ` Andi Kleen
2005-08-22 0:48 ` Steven Rostedt
2005-08-24 3:39 Steve French
2005-08-24 4:19 ` Hal Wigoda
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=20050822014956.GI5726@stusta.de \
--to=bunk@stusta.de \
--cc=Urban.Widmark@enlight.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba@samba.org \
--cc=sfrench@us.ibm.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
Powered by JetHome