Hi, On Wed, 4 Nov 2009, Sitaram Chamarty wrote: > It seems to me an accidental push -f would cause some trouble on a bare > repo, and would usually require a bit of grubbing around among the > unreachable commits looking for the right one. In one usage of mine, we have set said config value for exactly that reason. > What would be the downsides (other than some objects hanging > around far longer, i.e., space issues) of setting the config > variable core.logAllRefUpdates to be default true on bare > repos. I did not have time yet to investigate, but it seems that there are problems with the permissions of shared bare repositories when activating the reflogs. With gitweb on a public site, there might be a problem when you pushed some blob containing trade secrets accidentally, and try to scrub the repository using "git gc" after a forced push. That are the only downsides I can think of. Ciao, Dscho -- 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