From: Artem Bityutskiy <dedekind1@gmail.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Arno Steffen <arno.steffen@googlemail.com>
Subject: Re: NOTE! mkfs.ubifs
Date: Wed, 08 Sep 2010 11:18:19 +0300 [thread overview]
Message-ID: <1283933899.2979.56.camel@localhost> (raw)
In-Reply-To: <4C8612B9.4060305@nokia.com>
On Tue, 2010-09-07 at 13:23 +0300, Adrian Hunter wrote:
> I do not agree with changing the behaviour. It should be a new option,
> and you could add a warning explaining what the root inode permissions
> are and why e.g.
>
> Warning: Option ?? not used. Setting root inode permissions to blah
>
> Warning: Option ?? used. Setting root inode permissions to blah
Sent you v2 of this patch with an alternative (less harsh) solution.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-09-08 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:36 [PATCH] mkfs.ubifs: do not override root inode permissions Artem Bityutskiy
2010-09-07 9:11 ` NOTE! mkfs.ubifs Artem Bityutskiy
2010-09-07 10:23 ` Adrian Hunter
2010-09-08 5:55 ` Artem Bityutskiy
2010-09-08 8:18 ` Artem Bityutskiy [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=1283933899.2979.56.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=arno.steffen@googlemail.com \
--cc=linux-mtd@lists.infradead.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 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.