Jonathan Nieder <jrnieder@xxxxxxxxx> writes: > I'd be worried about using a clean filter to store timestamps. > Treating a file as changed whenever mtime changes could be confusing. > Treating atime changes as content changes would be even stranger. That is exactly why git does not store metainfo. Storing auxiliary information on commit objects or tree objects to help build or deploy procedures is fine, but that kind of information should be stored somewhere that the normal git operations would not care about. -- 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