From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Jeff King <peff@peff•net>
Cc: Hilco Wijbenga <hilco.wijbenga@gmail•com>,
Robin Rosenberg <robin.rosenberg@gmail•com>,
Kyle Moffett <kyle@moffetthome•net>,
Michael Witten <mfwitten@gmail•com>,
Junio C Hamano <gitster@pobox•com>,
Evan Shelhamer <shelhamer@imaginarynumber•net>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: Branches & directories
Date: Mon, 03 Oct 2011 09:41:29 +0200 [thread overview]
Message-ID: <vpqmxdiikt2.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20111003073456.GA10054@sigill.intra.peff.net> (Jeff King's message of "Mon, 3 Oct 2011 03:34:56 -0400")
Jeff King <peff@peff•net> writes:
> Speaking of which; does anybody know of a git-aware ccache-like tool?
> We already have a nice index of the sha1 of each file in the repository
> (along with a stat cache showing us whether it's up-to-date or not).
> Something like ccache could avoid even looking in the C files at all if
> it relied on git's index.
It would be a bit harder than that I think. IIRC, ccache hashes the
preprocessed file, hence it will notice if a .h file changed, even if
it's outside the project.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2011-10-03 7:41 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 18:35 Branches & directories Hilco Wijbenga
2011-08-17 18:47 ` Evan Shelhamer
2011-08-17 19:14 ` Junio C Hamano
2011-08-17 21:23 ` Hilco Wijbenga
2011-08-18 4:45 ` Jonathan Nieder
2011-08-21 19:48 ` Hilco Wijbenga
2011-08-18 5:52 ` Michael Witten
2011-08-18 10:56 ` Michael J Gruber
2011-08-18 17:49 ` Michael Witten
2011-08-19 0:13 ` Jonathan Nieder
2011-08-21 20:25 ` Hilco Wijbenga
2011-08-21 20:53 ` Michael Witten
2011-08-21 21:37 ` Hilco Wijbenga
2011-08-21 23:06 ` Michael Witten
2011-08-21 23:35 ` Hilco Wijbenga
2011-08-22 0:07 ` Michael Witten
2011-08-22 0:47 ` Hilco Wijbenga
2011-08-22 1:53 ` Hilco Wijbenga
2011-08-22 2:05 ` Michael Witten
2011-08-22 2:13 ` Hilco Wijbenga
2011-08-22 3:01 ` Kyle Moffett
2011-08-22 5:36 ` Hilco Wijbenga
2011-08-22 12:46 ` Kyle Moffett
2011-08-22 18:49 ` Hilco Wijbenga
2011-08-22 19:31 ` Kyle Moffett
2011-08-22 20:10 ` Hilco Wijbenga
2011-08-22 21:01 ` Restoring timestamps (Re: Branches & directories) Jonathan Nieder
2011-08-22 22:33 ` Hilco Wijbenga
2011-08-22 23:21 ` Jonathan Nieder
2011-08-23 3:06 ` Hilco Wijbenga
2011-08-23 3:20 ` Hilco Wijbenga
2011-10-02 15:06 ` Enrico Weigelt
2011-10-02 22:29 ` Hilco Wijbenga
[not found] ` <CA+sFfMf=gi5CWyfZEt-Nmdr4J9g__maQTqy1WePr1x8D-AVr4A@mail.gmail.com>
2011-10-02 22:25 ` Hilco Wijbenga
2011-08-23 14:46 ` Branches & directories Michael Witten
2011-10-02 16:57 ` Robin Rosenberg
2011-10-02 17:31 ` Ronan Keryell
2011-10-02 19:09 ` Matthieu Moy
2011-10-02 23:45 ` Hilco Wijbenga
2011-10-02 23:40 ` Hilco Wijbenga
2011-10-03 3:07 ` Jeff King
2011-10-03 7:15 ` Hilco Wijbenga
2011-10-03 7:30 ` Jeff King
2011-10-03 7:32 ` Matthieu Moy
2011-10-03 7:34 ` Jeff King
2011-10-03 7:41 ` Matthieu Moy [this message]
2011-10-03 7:44 ` Jeff King
2011-10-03 7:48 ` Junio C Hamano
2011-10-03 7:51 ` Jeff King
2011-10-03 17:31 ` Hilco Wijbenga
2011-10-03 14:59 ` Robin Rosenberg
2011-10-03 17:20 ` Hilco Wijbenga
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=vpqmxdiikt2.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=hilco.wijbenga@gmail$(echo .)com \
--cc=kyle@moffetthome$(echo .)net \
--cc=mfwitten@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=robin.rosenberg@gmail$(echo .)com \
--cc=shelhamer@imaginarynumber$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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