On Thu, 14 Dec 2006, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxx> writes: > > > I'd say screw that. The solution should really be this patch: > > > > diff --git a/environment.c b/environment.c > > index 84d870c..98275b2 100644 > > --- a/environment.c > > +++ b/environment.c > > @@ -15,7 +15,7 @@ int use_legacy_headers = 1; > > int trust_executable_bit = 1; > > int assume_unchanged; > > int prefer_symlink_refs; > > -int log_all_ref_updates; > > +int log_all_ref_updates = 1; > > int warn_ambiguous_refs = 1; > > int repository_format_version; > > char git_commit_encoding[MAX_ENCODING_LENGTH] = "utf-8"; > > > > That changes what the command does to existing repositories, > which is somewhat impolite. You must be kidding, aren't you? Just in case you really are serious, let's pretend that being impolite for something that has the potential of saving people's arses is certainly worth it, much more that the little inconvenience of having log files mysteriously appear and make no harm otherwise. > I am not opposed too much to an updated version of the tool that > sets the configuration on by default for newly created > repositories, though. Hmmm.... Well it is just that I strongly believe users with existing repos have no really valid reason to not have this feature enabled. But making it on in a default config file at repo creation time is better than nothing. Nicolas - 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