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-0.9.7-144-gd404c11 Date: Tue, 19 May 2009 18:16:00 -0000 [thread overview] Message-ID: <20090519181628.25382.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 d404c11425538c0af84a6ddecaa6652d0fe88085 (commit) via c0c1ccc66e32dcdf53983acbefb1c3a03eb1c2eb (commit) via bad69f1da34100f1822d0ffe58866f78b46c325b (commit) from c897e941ca645ab1e2aa325e5feaae30cc43060e (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 d404c11425538c0af84a6ddecaa6652d0fe88085 Author: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it> Date: Tue May 19 13:22:20 2009 +0200 Fix alignment of probe aliases in syscalls(|2).stp. Align probe points in probe aliases to equal sign using spaces as it's already done in nd_syscalls.stp. Signed-off-by: Josh Stone <jistone@redhat.com> commit c0c1ccc66e32dcdf53983acbefb1c3a03eb1c2eb Author: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it> Date: Tue May 19 13:04:29 2009 +0200 Unify formatting of syscalls.stp and syscalls2.stp. Rules: - Specify probe points for aliases starting from the alias declaration line and with one probe point per line. - Use K&R indent style -- probe alias/point/function opening brace goes to the line following the declaration, other opening braces are kept on the same line as the control statements. - Indent using tabs. - Surround operators with spaces. - Put spaces after commas. - Avoid trailing whitespaces. Signed-off-by: Josh Stone <jistone@redhat.com> commit bad69f1da34100f1822d0ffe58866f78b46c325b Author: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it> Date: Tue May 19 09:49:55 2009 +0200 Correct misnamed variables in syscalls.stp. Rename variables accordingly to argument names used in man pages in syscall.(faccess|fchmod|fchown|link|mknod)at probe points. Signed-off-by: Josh Stone <jistone@redhat.com> ----------------------------------------------------------------------- Summary of changes: tapset/syscalls.stp | 1591 +++++++++++++++++++++++++++----------------------- tapset/syscalls2.stp | 1597 ++++++++++++++++++++++++++++---------------------- 2 files changed, 1765 insertions(+), 1423 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-05-19 18:16 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=20090519181628.25382.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).