On Sat, 13 May 2006, Shawn Pearce wrote: > > Forget my last patch. This one automatically creates the log file > by looking for a config value of 'core.logRefUpdates=true'. Looks better. I actually disagree with Junio - I think the logging the name made sense. If you have a shared repo with multiple people pushing to the same branch, it's interesting to see who does the pushing. I also think it might be good to save the oldsha1 value. Yes, it _should_ always be the previous sha1 logged, but it's interesting to see in case it isn't (ie the ref was updated some other way), and it's also interesting for the first entry after logging has been enabled. Hmm? Linue - : 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