From: Eduardo Silva <eduardo.silva@oracle.com>
To: Hubert Kario <hka@qbs.com.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs new btrfs_error() macro to deprecate fprintf(stderr, ...)
Date: Thu, 10 Feb 2011 13:12:03 -0300 [thread overview]
Message-ID: <1297354323.28159.23.camel@monotop> (raw)
In-Reply-To: <201102101607.44204.hka@qbs.com.pl>
On Thu, 2011-02-10 at 16:07 +0100, Hubert Kario wrote:
> On Thursday, February 10, 2011 15:54:55 Eduardo Silva wrote:
> > Hi,
> >
> > This patch add a new macro called btrfs_error(...) which deprecate the
> > use of fprintf(stderr, ...)
> >
> > regards,
> >
> > Eduardo
>
> Sorry, but I don't see a reason for such change. IMHO it only makes the code
> _less_ readable.
>
> Regards,
no troubles :)
regards,
Ed.-
prev parent reply other threads:[~2011-02-10 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 14:54 [PATCH] Btrfs-progs new btrfs_error() macro to deprecate fprintf(stderr, ...) Eduardo Silva
2011-02-10 15:07 ` Hubert Kario
2011-02-10 16:12 ` Eduardo Silva [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=1297354323.28159.23.camel@monotop \
--to=eduardo.silva@oracle.com \
--cc=hka@qbs.com.pl \
--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).