From: Ian Kent <raven@themaw.net>
To: "Cyril B." <cbay@excellency.fr>
Cc: "autofs@vger.kernel.org" <autofs@vger.kernel.org>
Subject: Re: [PATCH] Add a --mode option to chmod the mount point of the maps
Date: Mon, 14 Sep 2015 11:23:06 +0800 [thread overview]
Message-ID: <1442200986.3030.45.camel@themaw.net> (raw)
In-Reply-To: <1442199959.3030.40.camel@themaw.net>
On Mon, 2015-09-14 at 11:05 +0800, Ian Kent wrote:
> On Sun, 2015-09-13 at 15:56 +0200, Cyril B. wrote:
> >
> > My solution was to add a --mode option to autofs, with the included
> > patch. I'm not familiar with autofs's code or even Lex and Yacc, so my
> > code is probably more of a proof of concept. It seems to work fine in my
> > use case, though.
>
> If you want to contribute patches then post then in-line as text without
> any additional change (eg. ensure the mailer doesn't split lines therby
> corrupting the patch).
>
> I can't properly comment on the patch, even if I wanted too, because it
> isn't in-line.
>
> Anyway, what about updating the man pages with your new option?
> Should text modes be considered, perhaps octal modes are sufficient, and
> should be all that's allowed, to keep the change as simple (generally a
> good idea) ...
And btw, I've been trying to ensure that all autofs patches have a
problem description for quite a long time now, so we need that too.
Generally describing what the change does isn't OK, a description of why
it's needed is more important and usually negates the need to describe
what the patch does.
Recently I've started adding "Signed-off-by:" annotation too.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2015-09-14 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 13:56 [PATCH] Add a --mode option to chmod the mount point of the maps Cyril B.
2015-09-14 2:31 ` Ian Kent
2015-09-14 8:42 ` Cyril B.
2015-09-14 9:20 ` Frank Thommen
2015-09-14 9:29 ` Cyril B.
2015-09-14 9:52 ` Ian Kent
2015-09-14 9:45 ` Ian Kent
2015-09-14 10:12 ` Cyril B.
2015-09-14 10:38 ` Ian Kent
2015-09-14 3:05 ` Ian Kent
2015-09-14 3:23 ` Ian Kent [this message]
2015-09-14 11:31 ` Cyril B.
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=1442200986.3030.45.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=cbay@excellency.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.