On 20/03/2012 12:04 pm, Jakub Narebski wrote:
The "matching" behavior is intende for non-symmetrical situation of a workflow where each user has its own separate public publishing repository, but can pull from many repositories from other developers (but never from one's own). The situation is assymetrical (even more that "pull" and "push" for single upstream repository, in a shared central repository case), so configuration is assymetrical.
Sorry, I wasn't clear enough. I'm well aware of why 'matching' and 'current' exist, and the workflows for which they're suited.
My point is that these bite new users before they've got to the point of developing workflows involving more than one remote. At that point, they're not aware of the need for an asymmetric config, so they're not expecting it to be the default.
To take another angle on it, I'd rather our new users said "Hey, there's an awesome config option that makes git play nicely with asymmetric workflows" than "Why on earth do pull and push interact with different remote branches by default".
Thanks, Antony -- 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