> IOW, my point is that branching should write the information it _knows_ > into the config: branch X was branched from branch Y. It should be up to > the programs to _use_ that information in a reasonable way. As it is > now, this patch makes the decision about how to use the information at > the time of branching, which seems to be the source of a lot of objects. 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. Paolo - 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