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-103-g4cd32d8 Date: Sat, 28 Jul 2012 16:56:00 -0000 [thread overview] Message-ID: <20120728165611.14654.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 4cd32d8c0ab8751fca058d2c6a9db8226c55ae65 (commit) from 0ed66feb1676dd8bdb3fba9643e0e597306e7f8d (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 4cd32d8c0ab8751fca058d2c6a9db8226c55ae65 Author: Josh Stone <jistone@redhat.com> Date: Sat Jul 28 09:55:10 2012 -0700 parse: Separate "empty or missing" file errors ... especially since there's a third state too: unreadable. * parse.cxx (parser::parser): Consolidate to a single ctor. (parse<istream>): Synthesize the name "<input>" to the parser from here. (parse<filename>): Open the file first, check its status, and if good only then pass the name and ifstream to the parser. (parser::parse): Now here the file is never missing, just empty. ----------------------------------------------------------------------- Summary of changes: parse.cxx | 39 +++++++++++++++++++-------------------- 1 files changed, 19 insertions(+), 20 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-28 16:56 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=20120728165611.14654.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).