From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/2][RFC] pruning libcman a bit
Date: Tue, 9 Oct 2012 20:31:26 +0200 [thread overview]
Message-ID: <1349807488-29871-1-git-send-email-jpokorny@redhat.com> (raw)
Hello,
I discovered two questionable places in libcman fixing of which has
a tiny simplification of code as a side-effect.
I tried my best to validate the changes (esp. the second changeset),
but would be great if someone reviewed the drafted thought-process
behind the changes as well as the actual changes.
Jan Pokorn? (2):
libcman: E{INTR,AGAIN} in cman_dispatch repeated read needs -1 too
libcman: remove superfluous cman_dispatch outer loop condition
cman/lib/libcman.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
--
1.7.11.4
next reply other threads:[~2012-10-09 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 18:31 Jan Pokorný [this message]
2012-10-09 18:31 ` [Cluster-devel] [PATCH 1/2] libcman: E{INTR, AGAIN} in cman_dispatch repeated read needs -1 too Jan Pokorný
2012-10-09 18:31 ` [Cluster-devel] [PATCH 2/2] libcman: remove superfluous cman_dispatch outer loop condition Jan Pokorný
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=1349807488-29871-1-git-send-email-jpokorny@redhat.com \
--to=jpokorny@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 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).