From: Kevin Cernekee <kpc.mtd@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] mkfs.ubifs: -U option does not take an argument
Date: Sat, 9 May 2009 23:41:33 -0700 [thread overview]
Message-ID: <372ea0a5bdff3415ed84e5f6666cd42c@localhost> (raw)
The long form (--squash-uids) is correct, but the short form (-U) is not.
Signed-off-by: Kevin Cernekee <kpc.mtd@gmail.com>
diff -ru mtd-utils.orig/mkfs.ubifs/mkfs.ubifs.c mtd-utils/mkfs.ubifs/mkfs.ubifs.c
--- mtd-utils.orig/mkfs.ubifs/mkfs.ubifs.c 2009-03-17 12:12:09.000000000 -0700
+++ mtd-utils/mkfs.ubifs/mkfs.ubifs.c 2009-05-09 23:37:19.000000000 -0700
@@ -128,7 +128,7 @@
/* Inode creation sequence number */
static unsigned long long creat_sqnum;
-static const char *optstring = "d:r:m:o:D:h?vVe:c:g:f:P:k:x:X:j:R:l:j:U:";
+static const char *optstring = "d:r:m:o:D:h?vVe:c:g:f:P:k:x:X:j:R:l:j:U";
static const struct option longopts[] = {
{"root", 1, NULL, 'r'},
next reply other threads:[~2009-05-10 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 6:41 Kevin Cernekee [this message]
2009-05-11 12:56 ` [PATCH] mkfs.ubifs: -U option does not take an argument Artem Bityutskiy
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=372ea0a5bdff3415ed84e5f6666cd42c@localhost \
--to=kpc.mtd@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