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-0.8-281-g0c44723
Date: Tue, 03 Feb 2009 17:35:00 -0000 [thread overview]
Message-ID: <20090203173530.18960.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 0c44723c0834224111db09284218d3104d149b44 (commit)
via c990eee01ecc5dcb8084dddcb0f69e799a3a3276 (commit)
via 6288515e1af7d7699628e2c4843f565938fa03a9 (commit)
via f5a40c83733a8270c1b9e991b8999e5fc8601e5f (commit)
via d777f0978faec5ee006deb83a15dec707e920c01 (commit)
via f9cf4e363d1372324bf83ca7fc0531319975cb18 (commit)
via 9e494cbb23b307d1e135fe188a894f0575c97abb (commit)
from a8cf6a4550d0e9197e668177ae09643c81b31791 (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 0c44723c0834224111db09284218d3104d149b44
Author: Dave Brolley <brolley@redhat.com>
Date: Tue Feb 3 12:34:41 2009 -0500
Touch up warning message from stap-client
commit c990eee01ecc5dcb8084dddcb0f69e799a3a3276
Merge: 6288515e1af7d7699628e2c4843f565938fa03a9 a8cf6a4550d0e9197e668177ae09643c81b31791
Author: Dave Brolley <brolley@redhat.com>
Date: Tue Feb 3 12:29:41 2009 -0500
Merge branch 'master' of git://sources.redhat.com/git/systemtap
Conflicts:
ChangeLog
commit 6288515e1af7d7699628e2c4843f565938fa03a9
Author: Dave Brolley <brolley@redhat.com>
Date: Tue Feb 3 12:28:18 2009 -0500
Document client/server certificate management and tools.
commit f5a40c83733a8270c1b9e991b8999e5fc8601e5f
Author: Dave Brolley <brolley@redhat.com>
Date: Mon Feb 2 16:14:03 2009 -0500
Use ps -e to look for stap server processes.
commit d777f0978faec5ee006deb83a15dec707e920c01
Merge: f9cf4e363d1372324bf83ca7fc0531319975cb18 0d65057a8a8b418568a18eb394d3e57f5a8051a5
Author: Dave Brolley <brolley@redhat.com>
Date: Mon Feb 2 16:00:01 2009 -0500
Merge branch 'master' of git://sources.redhat.com/git/systemtap
Conflicts:
ChangeLog
NEWS
commit f9cf4e363d1372324bf83ca7fc0531319975cb18
Author: Dave Brolley <brolley@redhat.com>
Date: Mon Feb 2 15:58:17 2009 -0500
Document latest changes.
commit 9e494cbb23b307d1e135fe188a894f0575c97abb
Author: Dave Brolley <brolley@redhat.com>
Date: Mon Feb 2 15:51:50 2009 -0500
Update NEWS and stap-server man page. Don't require client/server
platform compatibility for pahes 1-4.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 18 ++++
NEWS | 32 ++++---
stap-add-server-cert | 10 +-
stap-client | 7 +-
stap-server | 23 ++++--
stap-server.8.in | 230 +++++++++++++++++++++++++++++++++++++++++++++-----
stap-serverd | 2 +-
stap-stop-server | 2 +-
8 files changed, 271 insertions(+), 53 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2009-02-03 17:35 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=20090203173530.18960.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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).