From: Goffredo Baroncelli <kreijack@libero.it>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [TRIVIAL][PATCH] Improve error handling in the btrfs command
Date: Mon, 20 Dec 2010 23:53:29 +0100 [thread overview]
Message-ID: <201012202353.29222.kreijack@libero.it> (raw)
In-Reply-To: <4D0FDBE7.3070905@csamuel.org>
On Monday, 20 December, 2010, you (Chris Samuel) wrote:
> On 21/12/10 07:06, Goffredo Baroncelli wrote:
>
> > below is enclosed a trivial patch, which has the aim to
> > improve the error reporting of the "btrfs" command.
>
> Any reason to not just use perror() ?
Some time I needed to add other info, so perror(3) may not be sufficient..
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-12-20 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 20:06 [TRIVIAL][PATCH] Improve error handling in the btrfs command Goffredo Baroncelli
2010-12-20 22:42 ` Chris Samuel
2010-12-20 22:53 ` Goffredo Baroncelli [this message]
2010-12-21 0:29 ` Chris Samuel
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=201012202353.29222.kreijack@libero.it \
--to=kreijack@libero.it \
--cc=chris@csamuel.org \
--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