On Mon, 2010-12-06 at 11:51 -0600, Jonathan Nieder wrote: > Drew Northup wrote: > > On Fri, 2010-12-03 at 18:51 -0600, Jonathan Nieder wrote: > > >> Interesting. Setting "[core] trustctime = false" in the repository > >> configuration could be a good solution (no performance downside I can > >> think of). > > > > It is worth noting that many file-based backup systems which do "online" > > backups (such as in use where I work) restore the atime by default at > > the expense of the ctime (logic being that the atime may have had value > > and the ctime changes either way--which may or may not be true) on unix > > style filesystems. > > So have you tried putting "[core] trustctime = false" in /etc/gitconfig? > This is exactly what the setting is for, after all. I hadn't yet, but it works like a charm. > Ideas for making this easier to find (FAQ on the git wiki? advice from > porcelain when ctime-only changes happen?) would be welcome, of course. I'll have a look over that way a bit later. I'm also going to have to have a look at the src.rpm for this particular packaging of git and find out why it didn't create a skeleton /etc/gitconfig (without much in it) in the postinstall script. (I'm using the Dag Wieers / rpmforge one on my desktop.) It makes a lot more sense to send along a patch then randomly demand that he change it--he may have had a decent reason for not doing so. -- -Drew Northup N1XIM AKA RvnPhnx on OPN ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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