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.5-66-gb51455a
Date: Thu, 02 Apr 2009 19:30:00 -0000	[thread overview]
Message-ID: <20090402193045.19419.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  b51455af34a99768cc3a6ce50b251132f5fe752e (commit)
      from  a7d25c487ad74dc60bbbd93a2f689e0f0a047273 (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 b51455af34a99768cc3a6ce50b251132f5fe752e
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Apr 2 12:16:12 2009 -0700

    Disable ccache during kernel module builds
    
    Our module builds always have a 0% ccache hit rate, because the compiler
    commands always include the randomized tmpdir.  Thus, I'm setting
    CCACHE_DISABLE=1 so ccache never saves these one-use objects.
    
    (Besides, we already have our own caching in place for this stuff...)

-----------------------------------------------------------------------

Summary of changes:
 buildrun.cxx |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-04-02 19:30 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=20090402193045.19419.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: link
Be 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).