From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: git@vger.kernel.org
Subject: Re: Setting file timestamps to commit time (git-checkout)
Date: Wed, 11 Dec 2013 08:37:11 +0100 [thread overview]
Message-ID: <20131211073711.GA4848@linux.vnet.ibm.com> (raw)
In-Reply-To: <87bo0olebe.fsf@igel.home>
On Tue, Dec 10, 2013 at 08:02:29PM +0100, Andreas Schwab wrote:
> Dominik Vogt <vogt@linux.vnet.ibm.com> writes:
>
> > The second best approach I could think of is to stamp files with the
> > timestamp of the last commit that touched that, but I guess that is
> > not a cheap operation either.
>
> I'm using this script for this:
[snip]
Hm, that runs 18 s on the local Gcc repository. That's not as
expensive as I would have thought, but definitely not suitable to
run automatically on each checkout. I wonder if performance could
be improved by integrating the script logic into the git-checkout
code (activated by a command line option).
On Tue, Dec 10, 2013 at 05:39:05PM -0800, Constantine A. Murenin wrote:
> You can already do this with a very small third-party script:
>
> https://github.com/cnst/git-tools/blob/master/git-restore-mtime-core
That script just produces error messages for me.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2013-12-11 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 11:25 Setting file timestamps to commit time (git-checkout) Dominik Vogt
2013-12-09 20:35 ` Junio C Hamano
2013-12-10 8:35 ` Dominik Vogt
2013-12-10 19:02 ` Andreas Schwab
2013-12-11 7:37 ` Dominik Vogt [this message]
2013-12-11 1:39 ` Constantine A. Murenin
2013-12-09 20:48 ` Jonathan Nieder
2013-12-10 8:46 ` Dominik Vogt
2013-12-10 10:34 ` Duy Nguyen
2013-12-11 1:08 ` Jonathan Nieder
2013-12-11 1:01 ` Jonathan Nieder
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=20131211073711.GA4848@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.