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.1-41-g7437576 Date: Tue, 02 Feb 2010 13:30:00 -0000 [thread overview] Message-ID: <20100202133055.13411.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 743757687f9c09bf9ef84b576bc0aa0fc19dea4c (commit) via 241443ad36a5a2cacb9e8e6f12f808d304835f2a (commit) from cc57beca8d9d168ef42edb1f8b43f594105dfdf2 (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 743757687f9c09bf9ef84b576bc0aa0fc19dea4c Merge: 241443ad36a5a2cacb9e8e6f12f808d304835f2a cc57beca8d9d168ef42edb1f8b43f594105dfdf2 Author: Dave Brolley <brolley@redhat.com> Date: Tue Feb 2 08:28:16 2010 -0500 Merge branch 'master' of ssh://sources.redhat.com/git/systemtap commit 241443ad36a5a2cacb9e8e6f12f808d304835f2a Author: Dave Brolley <brolley@redhat.com> Date: Tue Feb 2 08:26:01 2010 -0500 PR 11105: Remaining client-side problems: stap-client: Correct handling of embedded newlines in arguments. server_args.exp: Add additional cases discovered by fche and by fuzzing. ----------------------------------------------------------------------- Summary of changes: stap-client | 88 +++++++++++++++------------- testsuite/systemtap.server/hello.stp | 2 +- testsuite/systemtap.server/server_args.exp | 6 ++ 3 files changed, 54 insertions(+), 42 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-02-02 13:30 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=20100202133055.13411.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).