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-211-ge91c276 Date: Wed, 14 Sep 2011 20:25:00 -0000 [thread overview] Message-ID: <20110914202553.29403.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 e91c276f51fa85a62f8e2996ff4b94909a2a14f7 (commit) from f98b79158876247b64e49158be6b8c60d8448142 (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 e91c276f51fa85a62f8e2996ff4b94909a2a14f7 Author: Dave Brolley <brolley@redhat.com> Date: Wed Sep 14 16:21:01 2011 -0400 Systemtap compile-server and client do not require avahi. Avahi is required for automatic detection and selection of compile-servers but the client can still contact servers directly without avahi. avahi-tools and avahi-devel are not required. Updated stap-start-server, testsuite/lib/systemtap.exp and systemtap.spec to reflect this. The specfile stills list avahi-client as a build requirement for both the systemtap and systemtap-server packages. ----------------------------------------------------------------------- Summary of changes: stap-start-server | 27 ++------------------------- systemtap.spec | 7 ++++--- testsuite/lib/systemtap.exp | 11 ----------- 3 files changed, 6 insertions(+), 39 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-14 20:25 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=20110914202553.29403.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).