On Fri, Mar 02, 2007 at 12:15:59PM +0100, Paolo Bonzini wrote: > > the time of branching, which seems to be the source of a lot of objects. Err, this should be "the source of a lot of objections" of course. > The problem is that this will pollute the configuration file a lot. > I'm starting to wonder if all this branch information really belongs > in .git/config at all. I'm not sure how this pollutes any more than the existing proposal. But I have always been a bit uncomfortable with automatic editing of the user config (having used such programs in the past, it always seems to cause subtle annoyances -- however, I find I don't even use the per-repo config in most cases, but just the ~/.gitconfig). Perhaps if we had an inclusion mechanism, all automatically written configuration could go into $GIT_DIR/auto_config with a big warning at the top, and the .git/config could include it. Or are you concerned with just polluting the config namespace? Obviously we could store per-branch metadata somewhere else, but I think there has been a push to put it _into_ the config over the past several months, instead of in a separate file. -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