All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: git-svn and incorrect working copy file timestamps?
@ 2009-03-19 23:02 Guido Ostkamp
  0 siblings, 0 replies; 3+ messages in thread
From: Guido Ostkamp @ 2009-03-19 23:02 UTC (permalink / raw)
  To: git, derek.mahar

> I learned from http://marc.info/?l=git&m=122783905206964&w=2 that all 
> Git commands do not preserve file timestamps because Git, by design, 
> does not record timestamps in the tree objects.  So, in order to see the 
> last time a particular file changed, you must examine the commit log. 
> I guess I'll just have to get used to ignoring the working copy file 
> timestamps.

As far as I know setting the current time is required when switching 
between different named branches in the same repository.

It can happen that a branch switch ('checkout' in Git's terminology) 
retrieves an older version of a source file, and then the Makefile would 
not detect that an object file (a result from earlier compilation that is 
of course not stored in the repo itself) has to be rebuild because this is 
based on time checks only. In order to avoid this, the source file (even 
if older) gets the current date, so it is in any case newer than the 
object file and causes an automatic rebuild.

Regards

Guido

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git-svn and incorrect working copy file timestamps?
  2009-03-19 19:54 Derek Mahar
@ 2009-03-19 21:31 ` Derek Mahar
  0 siblings, 0 replies; 3+ messages in thread
From: Derek Mahar @ 2009-03-19 21:31 UTC (permalink / raw)
  To: git

> Should "git svn" not preserve the file timestamps of the original commit tree
> in the working copy?

I learned from http://marc.info/?l=git&m=122783905206964&w=2 that all
Git commands do not preserve file timestamps because Git, by design,
does not record timestamps in the tree objects.  So, in order to see
the last time a particular file changed, you must examine the commit
log.  I guess I'll just have to get used to ignoring the working copy
file timestamps.

Derek

^ permalink raw reply	[flat|nested] 3+ messages in thread

* git-svn and incorrect working copy file timestamps?
@ 2009-03-19 19:54 Derek Mahar
  2009-03-19 21:31 ` Derek Mahar
  0 siblings, 1 reply; 3+ messages in thread
From: Derek Mahar @ 2009-03-19 19:54 UTC (permalink / raw)
  To: git


Should "git svn" not preserve the file timestamps of the original commit tree
in the working copy?  Using Git 1.6.2.1, built from source, I find that "git
svn clone" sets the file timestamps in the working copy to the current date. 
I expected the timestamps to match those of the tree as it was originally
committed.  I get this result using both Cygwin and Crunchbang Linux 8.10.02
(an Ubuntu derivative).

Derek
-- 
View this message in context: http://n2.nabble.com/git-svn-and-incorrect-working-copy-file-timestamps--tp2505059p2505059.html
Sent from the git mailing list archive at Nabble.com.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-03-19 23:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-03-19 23:02 git-svn and incorrect working copy file timestamps? Guido Ostkamp
  -- strict thread matches above, loose matches on Subject: below --
2009-03-19 19:54 Derek Mahar
2009-03-19 21:31 ` Derek Mahar

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.