From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 2/2] xfs_quota: fix report command parsing
Date: Fri, 9 Nov 2012 18:02:58 +1100 [thread overview]
Message-ID: <1352444578-14600-3-git-send-email-david@fromorbit.com> (raw)
In-Reply-To: <1352444578-14600-1-git-send-email-david@fromorbit.com>
From: Dave Chinner <dchinner@redhat.com>
The report command line needs to be parsed as a whole not as
individual elements - report_f() is set up to do this correctly.
When treated as non-global command line, the report function is
called once for each command line arg, resulting in reports being
issued multiple times.
Set the command to be a global command so that it is only called
once.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
---
quota/report.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/quota/report.c b/quota/report.c
index a1e165b..70894a2 100644
--- a/quota/report.c
+++ b/quota/report.c
@@ -653,6 +653,7 @@ report_init(void)
report_cmd.cfunc = report_f;
report_cmd.argmin = 0;
report_cmd.argmax = -1;
+ report_cmd.flags = CMD_FLAG_GLOBAL;
report_cmd.args = _("[-bir] [-gpu] [-ahnt] [-f file]");
report_cmd.oneline = _("report filesystem quota information");
report_cmd.help = report_help;
--
1.7.10
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-09 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 7:02 [PATCH 0/2] xfsprogs: fixes for release candidate Dave Chinner
2012-11-09 7:02 ` [PATCH 1/2] xfs_db: flush devices before exiting Dave Chinner
2012-11-13 17:45 ` Mark Tinguely
2012-11-09 7:02 ` Dave Chinner [this message]
2012-11-13 18:02 ` [PATCH 2/2] xfs_quota: fix report command parsing Mark Tinguely
2012-11-12 23:22 ` [PATCH 0/2] xfsprogs: fixes for release candidate Dave Chinner
2012-11-20 23:17 ` Mark Tinguely
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=1352444578-14600-3-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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