On Mon, 5 Mar 2007, Bill Lear wrote:
quoted text
> 
> Not because git wrote the file, but because git notices that content
> changes, and writes the file (and timestamps it) "smartly".  If
> someone writes into the repo, the timestamp stored becomes invalidated
> and the write of the file just creates the timestamp at the time of
> the checkout.  If no write into the repo index occurs, the stored
> timestamp is applied after the file is checked out.

But Bill, don't you realize that restoring the timestamp is *WRONG*?

There's no way that git can know whether you did a "make" in between 
switching back and forth between branches. That's true on a very 
fundamental level, but it's doubly true when anybody uses a separate 
object directory (which doesn't leave any information *at*all* in the 
source tree about the fact that somebody did a "make").

So stop even asking for this. We'd have to be totally and utterly 
incompetent to do what you ask for. We're simply not that stupid. 

We already pointed out how you can do what you want to do *other* ways 
that are *not* idiotic and incompetent. I don't think you even answered.

			Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html