From: "Steve French" <smfrench@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UID/GID override on CIFS mounts to Samba and proposed new mount parameter to disable Unix Extensions on the client
Date: Mon, 30 Apr 2007 15:27:57 -0500 [thread overview]
Message-ID: <524f69650704301327x72be0ba7h17cf8ce942dd9f04@mail.gmail.com> (raw)
In-Reply-To: <20070430083041.d460e946.randy.dunlap@oracle.com>
OK - I fixed the formatting and checked into the cifs-2.6.git tree. I
also fixed
a few dozen similar errors in formatting in the same files.
Thanks for noticing that.
On 4/30/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Mon, 30 Apr 2007 09:26:16 -0500 Steve French wrote:
>
> replying to the inline patch :(
>
> Use a space between "if" and "(" (multiple occurrences).
>
> Thanks.
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
--
Thanks,
Steve
prev parent reply other threads:[~2007-04-30 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 14:26 Steve French
2007-04-30 14:59 ` Anton Altaparmakov
2007-04-30 19:11 ` Steve French
2007-04-30 15:30 ` Randy Dunlap
2007-04-30 20:27 ` Steve French [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=524f69650704301327x72be0ba7h17cf8ce942dd9f04@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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
all inboxes | Powered by JetHome®