public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-142-g5ec722e Date: Sat, 04 Aug 2012 21:15:00 -0000 [thread overview] Message-ID: <20120804211523.27985.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 5ec722e14fb5d7f46c973adcdf8484165a97228a (commit) via e2d0f787a648eefe4e5a152058f92c3f3274242e (commit) via 0d98c8da13afc3e8345f6c62f7d848bdefe4dc71 (commit) from 49cb388809e44c017c2d7ade826ceaca38391a7f (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 5ec722e14fb5d7f46c973adcdf8484165a97228a Author: Josh Stone <jistone@redhat.com> Date: Sat Aug 4 14:12:33 2012 -0700 Don't print usage text on stap option errors The help text is so long that it tends to push the actual error message off the screen. Instead, just print a suggestion to consult --help. commit e2d0f787a648eefe4e5a152058f92c3f3274242e Author: Josh Stone <jistone@redhat.com> Date: Sat Aug 4 13:40:27 2012 -0700 PR14432: Convert stap exit() calls to exceptions We need the opportunity to clean up after ourselves, for example removing any temporary directories created. Calling exit() bypasses our usual exception/RAII-based cleanups, so don't do that. * session.h (exit_exception): New, an exception with a custom exit code. * main.cxx (main): We can simply return here. Also catch exit_exception. * session.cxx (systemtap_session::usage): Throw an exit_exception. (systemtap_session::parse_cmdline): Ditto. * util.cxx (assert_regexp_match): A runtime_error makes more sense here. commit 0d98c8da13afc3e8345f6c62f7d848bdefe4dc71 Author: Josh Stone <jistone@redhat.com> Date: Sat Aug 4 13:37:48 2012 -0700 DRY: get NLS definitions in session.h from util.h ----------------------------------------------------------------------- Summary of changes: main.cxx | 14 +++++++++----- session.cxx | 25 ++++++++++++++++++------- session.h | 22 +++++++++------------- util.cxx | 8 +++----- 4 files changed, 39 insertions(+), 30 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-04 21:15 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=20120804211523.27985.qmail@sourceware.org \ --to=jistone@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).