public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-28-g9fe3e54 Date: Fri, 30 Jul 2010 17:32:00 -0000 [thread overview] Message-ID: <20100730173215.13974.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 9fe3e54ab1225a382355661fbe5b1e3ee12b6828 (commit) via 3963dacdfe18d4fe956ae55fa5458351fb537543 (commit) from 398d19732c388bee486e4c568976296679378a00 (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 9fe3e54ab1225a382355661fbe5b1e3ee12b6828 Author: Frank Ch. Eigler <fche@elastic.org> Date: Fri Jul 30 13:31:55 2010 -0400 bump AUTHORS commit 3963dacdfe18d4fe956ae55fa5458351fb537543 Author: Kapileshwar Singh (KP) <kapileshwarsingh@gmail.com> Date: Fri Jul 30 13:29:32 2010 -0400 PR11861: tolerate null struct bio->bi_vcnt in __bio_ino tapset fn Jeff Moyer confirms operations such as blkdev_issue_flush can submit an empty bio. ----------------------------------------------------------------------- Summary of changes: AUTHORS | 1 + tapset/ioblock.stp | 2 +- 2 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-07-30 17:32 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=20100730173215.13974.qmail@sourceware.org \ --to=fche@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).