public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: brolley@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-544-g933e53b Date: Mon, 05 Dec 2011 17:37:00 -0000 [thread overview] Message-ID: <20111205173710.17356.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 933e53b0652f2e86c59e41073813731c6f877acc (commit) from 8beafa45f6c3660d152160c80e2dd3cba2166597 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 933e53b0652f2e86c59e41073813731c6f877acc Author: Dave Brolley <brolley@redhat.com> Date: Mon Dec 5 12:35:00 2011 -0500 PR 13323: staprun should check return code from send_request when sending messages via the transport layer The return code of send_request is now propagated and checked back to init_staprun. ----------------------------------------------------------------------- Summary of changes: runtime/staprun/common.c | 15 ++++--- runtime/staprun/mainloop.c | 13 +++++- runtime/staprun/relay.c | 2 +- runtime/staprun/staprun.c | 95 +++++++++++++++++++++++++++++------------- runtime/transport/control.c | 4 +- 5 files changed, 88 insertions(+), 41 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-05 17:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111205173710.17356.qmail@sourceware.org \ --to=brolley@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).