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.3-136-g2fccf42 Date: Thu, 16 Sep 2010 19:16:00 -0000 [thread overview] Message-ID: <20100916191640.15484.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 2fccf42c60b5b9c0e26fab030ec8411356bc91c3 (commit) via ed1719be6790515c42a66411680cb46175096a0b (commit) from 70036bd6757d815aee9529985ba21c335de580ff (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 2fccf42c60b5b9c0e26fab030ec8411356bc91c3 Author: Dave Brolley <brolley@redhat.com> Date: Thu Sep 16 15:14:52 2010 -0400 Correct recent change for finding the server cert database in stap-sign-module. commit ed1719be6790515c42a66411680cb46175096a0b Author: Dave Brolley <brolley@redhat.com> Date: Thu Sep 16 14:28:31 2010 -0400 Handle missing and empty client side certificate databases. ----------------------------------------------------------------------- Summary of changes: csclient.cxx | 46 +++++++++++++++++++++++++++++++--------------- modsign.cxx | 2 +- stap-client-connect.c | 8 ++++++-- 3 files changed, 38 insertions(+), 18 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-09-16 19:16 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=20100916191640.15484.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).