From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: Fix --squash-rino-perm / --nosquash-rino-perm
Date: Fri, 24 Sep 2010 11:51:07 +0300 [thread overview]
Message-ID: <1285318267.29268.164.camel@localhost> (raw)
In-Reply-To: <1a602213cef25044c025cc1aaf873cf5@localhost>
On Thu, 2010-09-23 at 15:58 -0700, Kevin Cernekee wrote:
> This addresses a couple of issues:
>
> 1) Code was only allowing these options if --root was NOT specified (the
> opposite of the documented usage)
>
> 2) -q / -Q short options did not work
>
> 3) Spacing fixes in the error/warning strings
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> mkfs.ubifs/mkfs.ubifs.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
Oh, yeah, thanks, pushed!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-09-24 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:58 [PATCH] mkfs.ubifs: Fix --squash-rino-perm / --nosquash-rino-perm Kevin Cernekee
2010-09-24 8:51 ` 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=1285318267.29268.164.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).