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-203-g3845290 Date: Tue, 13 Sep 2011 15:12:00 -0000 [thread overview] Message-ID: <20110913151212.26024.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 3845290458cd498e490078318ae5306911cb47a9 (commit) via 87e00d4e2c4c0a7a9f8f0679f54b0ae6da3e706a (commit) from 7c7971f5df049cfec2e1d5eaee4795de0e439030 (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 3845290458cd498e490078318ae5306911cb47a9 Author: Dave Brolley <brolley@redhat.com> Date: Tue Sep 13 11:07:11 2011 -0400 RHBZ 737095: Unable to start a systemtap server - Don't use getlogin to obtain user name because it can fail. - Establish server log before issuing any messages. - Failure of avahi to advertise is now only a warning. Avahi is not always available and the server can still be used directly. commit 87e00d4e2c4c0a7a9f8f0679f54b0ae6da3e706a Author: Dave Brolley <brolley@redhat.com> Date: Tue Sep 13 11:05:47 2011 -0400 Don't expose local path names in test names. ----------------------------------------------------------------------- Summary of changes: stap-serverd.cxx | 44 ++++++++++++++---------- stap-start-server | 21 ++++++----- testsuite/systemtap.server/client_args.exp | 50 ++++++++++++++-------------- 3 files changed, 61 insertions(+), 54 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-13 15:12 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=20110913151212.26024.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).