From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. ea639f2ff80acd22e6c1273932c24a456f947b0d
Date: Tue, 05 Mar 2013 01:30:16 +0100 [thread overview]
Message-ID: <20130305003017.D60122010D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
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 "IPFire 3.x development tree".
The branch, master has been updated
via ea639f2ff80acd22e6c1273932c24a456f947b0d (commit)
from 0f5c5df0ea3724c36552719fa494464f17575466 (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 ea639f2ff80acd22e6c1273932c24a456f947b0d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Mar 5 01:28:36 2013 +0100
ccache: Set CCACHE_HASHDIR.
To properly be able to debug problems with gdb, this
must be set to an empty value.
-----------------------------------------------------------------------
Summary of changes:
ccache/ccache.nm | 2 +-
ccache/ccache.sh | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/ccache/ccache.nm b/ccache/ccache.nm
index ad42d4a..a7d1ea1 100644
--- a/ccache/ccache.nm
+++ b/ccache/ccache.nm
@@ -5,7 +5,7 @@
name = ccache
version = 3.1.9
-release = 1
+release = 2
groups = Development/Compilers
url = http://ccache.samba.org/
diff --git a/ccache/ccache.sh b/ccache/ccache.sh
index 603434b..e89c126 100644
--- a/ccache/ccache.sh
+++ b/ccache/ccache.sh
@@ -16,3 +16,4 @@ if [ -z "${CCACHE_DIR:-}" ] && [ -w @CACHEDIR@ ] && [ -d @CACHEDIR@ ] ; then
unset CCACHE_HARDLINK
fi
+export CCACHE_HASHDIR=
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-03-05 0: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=20130305003017.D60122010D@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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