From: "Randy.Dunlap" <rddunlap@osdl.org>
To: haroldo.gamal@silexonline.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Submitting patches for unmaintained areas (Solaris x86 UFS bug)
Date: Wed, 13 Oct 2004 08:05:16 -0700 [thread overview]
Message-ID: <416D442C.5070305@osdl.org> (raw)
In-Reply-To: <416D1D6F.4080508@silexonline.org>
Haroldo Gamal wrote:
> I've done have done the same with
> http://bugzilla.kernel.org/show_bug.cgi?id=3330 and I have the same
> question!
>
> Where do I go from now?
Have you tried contacting the SMBfs maintainer?
from the MAINTAINERS file:
SMB FILESYSTEM
P: Urban Widmark
M: urban@teststation.com
W: http://samba.org/
L: samba@samba.org
S: Maintained
--
~Randy
next prev parent reply other threads:[~2004-10-13 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 11:06 Submitting patches for unmaintained areas (Solaris x86 UFS bug) Alex Kiernan
2004-10-13 12:10 ` Alex Kiernan
2004-10-13 13:43 ` viro
2004-10-15 16:35 ` Alex Kiernan
2004-10-18 10:20 ` Alex Kiernan
2004-10-19 8:21 ` Alex Kiernan
2004-10-13 12:19 ` Haroldo Gamal
2004-10-13 15:05 ` Randy.Dunlap [this message]
2004-10-14 11:16 ` Haroldo Gamal
2004-10-14 15:15 ` Randy.Dunlap
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=416D442C.5070305@osdl.org \
--to=rddunlap@osdl.org \
--cc=haroldo.gamal@silexonline.org \
--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