From: Petr Baudis <pasky@ucw.cz>
To: GIT <git@vger.kernel.org>
Subject: Re: Howto get repository up2date after pull with touching as less as possible files in the working directory
Date: Mon, 9 May 2005 20:18:42 +0200 [thread overview]
Message-ID: <20050509181842.GA7040@pasky.ji.cz> (raw)
In-Reply-To: <20050509174951.GK24216@cip.informatik.uni-erlangen.de>
Dear diary, on Mon, May 09, 2005 at 07:49:51PM CEST, I got a letter
where Thomas Glanzmann <sithglan@stud.uni-erlangen.de> told me that...
> Hello alltogether,
> at the moment I ensrure that there are no dirty files before the pull
> and do a
>
> git-read-tree HEAD
> git-checkout -a -f
> git-update-cache --refresh
>
> this is suboptimal because all the files in my working directory get a
> new timestamp and if I call make everything is recompiled (ccache helps,
> but is not the solution to this problem).
Do git-read-tree -m HEAD instead. That will keep the original stat
information and checkout will rewrite only files it needs to.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
prev parent reply other threads:[~2005-05-09 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 17:49 Howto get repository up2date after pull with touching as less as possible files in the working directory Thomas Glanzmann
2005-05-09 18:18 ` Petr Baudis [this message]
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=20050509181842.GA7040@pasky.ji.cz \
--to=pasky@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox