From: Josh Berry <des@condordes.net>
To: kreijack@libero.it
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] Move all btrfs command to only one command
Date: Fri, 20 Aug 2010 11:27:05 -0700 [thread overview]
Message-ID: <AANLkTinfTtUvYSf7u0F8vE4BK_7891u1Cr7irc8FdUaa@mail.gmail.com> (raw)
In-Reply-To: <201008201403.41330.kreijack@libero.it>
On Fri, Aug 20, 2010 at 05:03, Goffredo Baroncelli <kreijack@gmail.com>=
wrote:
> On Thursday, 19 August, 2010, James Smith wrote:
>> This patch randomizes the error codes and also fixes up some typos
> including
>> capitalization in the output.
>>
>> It would almost be nice to see a translation effort for the tool as =
well.
[...]
>
> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 fprintf(stderr, "ERR-A.11: in command '");
>
> I am not against this kind of error codes, but I prefer
>
> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 fprintf(stderr, "Error 'ERR-A.11' in command '");
As a layman/end user, I disagree. The former format is easier for
shell scripts and the like to parse -- the error code can be extracted
with a simple "cut -d: -f1".
(In fact, I wish the output from things like "btrfs filesystem df",
"show", etc. were easier to parse, but that's a separate issue. :) )
-- Josh
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-20 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:52 [RFC] Move all btrfs command to only one command James Smith
2010-08-20 12:03 ` Goffredo Baroncelli
2010-08-20 12:43 ` Jon Nelson
2010-08-20 14:42 ` Benjamin Griese
2010-08-20 18:56 ` Goffredo Baroncelli
2010-08-20 18:27 ` Josh Berry [this message]
2010-08-20 18:34 ` Andreas Philipp
2010-08-20 18:49 ` Josh Berry
2010-08-20 19:00 ` Andreas Philipp
2010-08-20 20:28 ` Josh Berry
2010-08-21 4:51 ` James Smith
2010-08-21 9:37 ` Goffredo Baroncelli
[not found] ` <AANLkTikJd8bDU1Eq22u0+yQ8eBCUn3OXHoE5E7uy+SG=@mail.gmail.com>
[not found] ` <AANLkTi=VpZv26jntJ8mwmxtjnQ5LDOn_MSm6VtEhJ1CB@mail.gmail.com>
2010-08-27 3:38 ` James Smith
2010-08-20 19:03 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2010-08-20 12:12 Goffredo Baroncelli
2010-01-21 19:29 Goffredo Baroncelli
2010-01-22 0:02 ` TARUISI Hiroaki
2010-01-22 0:11 ` Michael Niederle
2010-01-22 9:33 ` Xavier Nicollet
2010-01-22 8:23 ` Adrian von Bidder
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=AANLkTinfTtUvYSf7u0F8vE4BK_7891u1Cr7irc8FdUaa@mail.gmail.com \
--to=des@condordes.net \
--cc=kreijack@libero.it \
--cc=linux-btrfs@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).