On 2 October 2011 12:09, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Ronan Keryell <Ronan.Keryell@xxxxxxxxxxxxxxx> writes: > >>>>>>> On Sun, 02 Oct 2011 18:57:55 +0200, Robin Rosenberg <robin.rosenberg@xxxxxxxxx> said: >> >> Robin> Hilco Wijbenga skrev 2011-08-22 22.10: >> >> [...] I just wish there was at least an option to keep the >> >> timestamp (and possibly other such things). Even Subversion can >> >> do that... ;-) After all, not everybody uses C& make. > > AFAIK, Subversion doesn't version timestamps. What it can do is to set > the timestamp to the commit date at the time the file is checked-out. Correct and this would fix my problem, I believe. >> Robin> What tools do you use that need the benefits from retaining >> Robin> timestamps? The only one I can think of is clearmake, but >> Robin> then that tool goes with another SCM. Eclipse, for example, >> Robin> will be just as confused by timestamps that travel backwards >> Robin> in time, as make is. >> >> I think of tools called "humans", very common indeed on Earth. :-) > > For human beings, it's not really harder to run > > git log -1 file I think the idea is that computers do the work, not humans... :-) > than to look at the on-disk timestamp. And it continues working after > you start modifying the file, so it's much less fragile than the > filesystem timestamp. > > But if you insist in reproducing SVN's "use-commit-times = yes" setting, > it should be doable with a post-checkout hook. Mmm, this post-checkout hook would get the commit time from the commit and "touch" all relevant files with that timestamp? Is that easily done? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html