public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: wcohen@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-258-gb01b488 Date: Mon, 14 Jun 2010 14:34:00 -0000 [thread overview] Message-ID: <20100614143403.5900.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 b01b4888eaf34e02514d86acf905d36c62497f32 (commit) from bfcb3aac4632f7f6ae64d043cb2958eaaea53af5 (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 b01b4888eaf34e02514d86acf905d36c62497f32 Author: William Cohen <wcohen@redhat.com> Date: Mon Jun 14 10:30:06 2010 -0400 Make sure that the tapset documentation title descriptions are on a single line The docproc program that extracts information information from the tapset comments needs the title line to be a single line. Otherwise the second line get counted as a description line and conflicts with the later "Description:" section. ----------------------------------------------------------------------- Summary of changes: tapset/ansi.stp | 3 +-- tapset/context.stp | 24 ++++++++---------------- tapset/conversions.stp | 21 +++++++-------------- tapset/memory.stp | 3 +-- tapset/string.stp | 6 ++---- 5 files changed, 19 insertions(+), 38 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-14 14:34 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=20100614143403.5900.qmail@sourceware.org \ --to=wcohen@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).