From: "Guillaume Boissiere" <boissiere@attbi.com>
To: Urban Widmark <urban@teststation.com>
Cc: <linux-kernel@vger.kernel.org>,
Guillaume Boissiere <boissiere@attbi.com>
Subject: Re: LFS support for smbfs in 2.5, and other improvements
Date: Sat, 9 Mar 2002 10:56:31 -0500 [thread overview]
Message-ID: <3C89EA5F.16379.4752E3A@localhost> (raw)
In-Reply-To: <20020309005423.GB896@matchmail.com>
In-Reply-To: <Pine.LNX.4.33.0203091109140.21120-100000@cola.teststation.com>
> Using the terminology from the status page I guess this could be the smbfs
> list:
>
> Alpha smbfs: I/O rewrite, smbiod
> Alpha smbfs: Fcntl locking + smb oplock support
> Alpha smbfs: smbconnect for better fstab integration
> Planning smbfs: Readahead support (async readpage/writepage)
> Planning smbfs: Read/Write request merging
>
> But won't the list become very long if every little driver included all
> the planned changes? Not my problem I guess ...
Yes, I am trying to limit the status list to the big items so that it
stays readable for people.
> Also I don't know if any of this will be ready to be merged within the 6
> month limit mentioned in one of the early announcements.
Why don't we do this, if there is anything that gets close to inclusion
and you feel it is a big thing lots of people have been anxiously waiting
for, let me know and I'll put it in.
> Regarding the updated statuspage, it isn't the "Samba filesystem", it is
> the SMB filesystem (usually smbfs, SMBFS, SMBfs and possibly other
> variations).
Fixed, thanks.
-- Guillaume
next prev parent reply other threads:[~2002-03-09 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 0:54 LFS support for smbfs in 2.5, and other improvements Mike Fedyk
2002-03-09 11:01 ` Urban Widmark
2002-03-09 15:56 ` Guillaume Boissiere [this message]
[not found] <20020309005003.GA896@matchmail.com>
2002-03-09 5:38 ` Guillaume Boissiere
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=3C89EA5F.16379.4752E3A@localhost \
--to=boissiere@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=urban@teststation.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