From: Benno Schulenberg <bensberg@justemail.net>
To: Karel Zak <kzak@redhat.com>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: RFC [patch] adding docstrings
Date: Sat, 20 Dec 2014 15:42:54 +0100 [thread overview]
Message-ID: <1419086574.2592978.205177769.60905F6A@webmail.messagingengine.com> (raw)
In-Reply-To: <20141219090925.GI19904@x2.net.home>
On Fri, Dec 19, 2014, at 10:09, Karel Zak wrote:
> On Wed, Dec 17, 2014 at 09:20:31PM +0100, Benno Schulenberg wrote:
> > For mkfs.cramfs, mkfs.minix, blkid and chrt I've had to
> > improvise -- putting the docstring before the synopis -- in order to
> > avoid making extensive changes to the usage text; those changes will
> > come later.)
>
> hmm.. it would be better to be consistent and add the docstring to the
> same position in all utils.
Certainly. These improvisations were meant as temporary measures.
A later patch would slice up and standardize the usage texts of the
mentioned utils and put the docstring into its proper place -- I just
wanted to avoid burdening this patch with such extensive and fairly
unrelated changes.
Probably it is better not to make temporary changes, so I will drop
the docstrings for the mentioned tools from the next version of the
patch.
By the way, there was some talk of obsoleting / scrapping / deleting
some of the utils. Are there still such plans? If so, it is maybe
better not to add docstrings for the tools that are going to be zapped
in the next cycle or so?
> you forgot _() NLS macro:
>
> > + fputs("Tell the kernel about the existence of a specified partition.\n", out);
Thanks.
Benno
--
http://www.fastmail.com - Or how I learned to stop worrying and
love email again
next prev parent reply other threads:[~2014-12-20 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:20 RFC [patch] adding docstrings Benno Schulenberg
2014-12-18 9:20 ` Adam Sampson
2014-12-18 20:29 ` Benno Schulenberg
2014-12-19 9:09 ` Karel Zak
2014-12-20 14:42 ` Benno Schulenberg [this message]
2014-12-22 10:11 ` Karel Zak
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=1419086574.2592978.205177769.60905F6A@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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).