From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/2] libgfs2: Expand out calls to die()
Date: Wed, 14 Dec 2011 17:14:21 +0000 [thread overview]
Message-ID: <4EE8D96D.60500@redhat.com> (raw)
In-Reply-To: <1323880882.2860.24.camel@menhir>
On 14/12/11 16:41, Steven Whitehouse wrote:
> Hi,
>
> Those look like a good start, but we also need to figure out how to push
> the error handling back into the apps too,
Yes, I made a tentative start on this a while ago. Each libgfs2 function
which calls exit() will need all of its callers (and their callers, and
their...) updating so it's going to take a fair deal more work.
If we're agreed on the convention of setting errno and returning
non-zero (or non-valid values) to flag errors, then the way forward is
reasonably clear.
Andy
next prev parent reply other threads:[~2011-12-14 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 16:20 [Cluster-devel] [PATCH 1/2] libgfs2: Expand out calls to die() Andrew Price
2011-12-14 16:20 ` [Cluster-devel] [PATCH 2/2] libgfs2: Push down die() into the utils and remove it Andrew Price
2011-12-14 16:23 ` [Cluster-devel] [PATCH 1/2] libgfs2: Expand out calls to die() Bob Peterson
2011-12-14 16:41 ` Steven Whitehouse
2011-12-14 17:14 ` Andrew Price [this message]
2011-12-14 17:22 ` Steven Whitehouse
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=4EE8D96D.60500@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.