Jeff King <peff@xxxxxxxx> writes: > But I don't buy this at all. It is totally dependent on workflow and how > you use branches. Of course. "Encouraging a behaviour" means just that. A better workflow and a better use of branches. > When you think about "is my current branch ready to push?" there is no > reason for you to think of that other long-running branch that you > haven't seen for days. Sorry, I have to disagree with that. We are talking about people to whom the "push matching refs" is a problem, and that means they are using a branch with the same name with other people (either from a shared central repository or his own publishing branch) to house long-running, intermediate, uncooked state. Why aren't you forking off your own topic branch from such a branch that is either shared (or for publishing)? For the purpose of this discussion, shared branch is the same as your own publishing branch -- that's where you put things that are *ready* to be seen by other people. The one you haven't seen for days, if it is not shared, won't bother you nor your "matching push", because you wouldn't have merged your uncooked changes from your own topic branch to that shared branch yet. -- 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
