On Wed, Nov 19, 2008 at 05:18:16PM +0100, Christian MICHON wrote: > On Wed, Nov 19, 2008 at 12:37 PM, Roger Leigh <rleigh@xxxxxxxxxxxxx> wrote: > > Would it be possible for git to store the mtime of files in the tree? > > > > This would make it possible to do this type of work in git, since it's > > currently a bit random as to whether it works or not. This only > > started when I upgraded to an amd64 architecture from powerpc32, > > I guess it's maybe using high-resolution timestamps. > > > > beside the obvious answer it comes back often as a request, it is > possible in theory to create a shell script which, for each file > present in the sandbox in the current branch, would find the mtime of > the last commit on that file (quite an expensive operation) and apply > it. Surely this is only expensive because you're not already storing the information in the tree; if it was there, it would be (relatively) cheap? You could even compare the old and new trees to see if you needed to touch a file at all. > You should store mostly content of source files. You should do a make > in your first cloned repo at least once before committing anything to > the repo. That's what I did and I saved days... Except in this case I'm storing the content of *tarballs* (along with pristine-tar). I'm committing exactly what's in the tarball with no changes (this is a requirement). I can't change the source prior to commit. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Attachment:
signature.asc
Description: Digital signature
