On Thu, Jan 13, 2011 at 04:12:25AM +0100, Tomas Carnecky wrote: > On 1/12/11 3:07 PM, Maaartin wrote: > >There are files in my working tree which changes, but their size and mtime > >remains the same (I know it's strange, but it's useful). Can I make git to re- > > When can this be useful? > > >read them all, so it recognizes the change? Ideally, using a configuration > >variable. The repo is fairly small, so speed is no issue here. > > Try git update-index --refresh. I'm not aware of any config option, > but you might want to look through man git-config. That won't work, as it respects the stat information. So does --really-refresh. AFAIK, there isn't a way to tell update-index to ignore start information, short of blowing away the index entirely, and doing a read-tree to repopulate it. I'm curious what this use case is, and whether it would be acceptable to update something like ctime on the files to make them stat-dirty to git. -Peff -- 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