git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Howto get repository up2date after pull with touching as less as possible files in the working directory

From
Petr Baudis <pasky@ucw.cz>
Date
May 9, 2005, 18:18 UTC
Message-ID
<20050509181842.GA7040@pasky.ji.cz>
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...

Show 11 quoted lines
> 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
Previous: Thomas Glanzmann
Message 2 of 2 in “Howto get repository up2date after pull with touching as less as possible files in the working directory”
  1. Thomas GlanzmannMay 9, 2005
  2. Petr BaudisMay 9, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.