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-0.7-549-g224e23b Date: Wed, 26 Nov 2008 22:43:00 -0000 [thread overview] Message-ID: <20081126224314.10723.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 224e23bef7a46c823c4b3d41efdf9dbf98853ed0 (commit) via 62794910c3ec360552209063fc2b9295e3382ca3 (commit) from 557320bbd95429836d2a077ac81337fcc3d3d354 (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 224e23bef7a46c823c4b3d41efdf9dbf98853ed0 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Nov 26 17:42:45 2008 -0500 safety: add another schedule_sched, ahead of the per-context release loop commit 62794910c3ec360552209063fc2b9295e3382ca3 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Nov 26 17:39:33 2008 -0500 PR4886: enable assertive build-id checking for new kernels ----------------------------------------------------------------------- Summary of changes: ChangeLog | 4 ++++ runtime/ChangeLog | 6 ++++++ runtime/sym.c | 13 +++++++++++-- translate.cxx | 9 +++++++-- 4 files changed, 28 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-11-26 22:43 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=20081126224314.10723.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).