On Wed, Jul 11, 2007 at 19:42:10 +0100, Johannes Schindelin wrote: > Hi list, > > > > > How difficult is it to have script (or maybe existing git option) > > > > that would make mtimes of all working files equal to time of last > > > > commit ? > > Now I slowly get really curious. Does _anybody_ know a scenario where > this makes sense? > > (No, Eric, there are enough corner cases where your example of a clustered > webserver breaks down, so I am not fully convinced that this is a useful > case.) > > Anybody enlighten me? I don't see any case where it would be useful, though I know some version control systems that provide that feature. I think it is supposed to just be used for checking which view has newer version. I first thought the idea had something to do with make, but it will actually promptly break most build tools, because change to earlier version is a change too, but they wouldn't detect it. However I am getting really curious about different thing -- the solution. Because I think the arguments from keyword expansion discussion apply here that prevent any *reliable* (you can have unreliable ones just as you can have unreliable keyword expansion) solution. -- Jan 'Bulb' Hudec <bulb@xxxxxx>
Attachment:
signature.asc
Description: Digital signature