From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] mkfs.gfs2: Improve strings for translation
Date: Fri, 16 Nov 2012 13:09:57 +0000 [thread overview]
Message-ID: <50A63B25.1020606@redhat.com> (raw)
In-Reply-To: <1353057944.2731.15.camel@menhir>
On 16/11/12 09:25, Steven Whitehouse wrote:
> Hi,
>
> I think that looks ok. One thought is whether it would be possible to
> merge the argument parsing (and the help message) for the three-in-one
> binary that we have at the moment. If we have arguments to set the mode
> (so we can override the default provided by the binary name) then it
> should be possible provided the options are not too different between
> the three,
It seems there are enough subtle differences (such as using different
getopt features) between the three tools that making the option parsing
code shared would be more trouble than it's worth. It should be fairly
simple to merge each tool's option parsing and help printing code but I
don't think it would buy us much so I'll leave it for now.
Andy
prev parent reply other threads:[~2012-11-16 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:57 [Cluster-devel] [PATCH] mkfs.gfs2: Improve strings for translation Andrew Price
2012-11-16 9:25 ` Steven Whitehouse
2012-11-16 13:09 ` Andrew Price [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=50A63B25.1020606@redhat.com \
--to=anprice@redhat.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;
as well as URLs for NNTP newsgroup(s).