Johannes Sixt <j...@kdbg.org> writes: > Again: Why not just define +refspec as the way to achieve this check?
What justification do we have to break existing people's configuration that says something like: [remote "ko"] url = kernel.org:/pub/scm/git/git.git push = master push = next push = +pu push = maint by adding a _new_ requirement they may not be able to satisify? Notice that the above is a typical "push only" publishing point, where you do not need any remote tracking branches. I am not opposed if your proposal were to introduce a new syntax element that calls for this new feature, e.g. [remote "ko"] url = kernel.org:/pub/scm/git/git.git push = *pu fetch = +refs/heads/*:refs/remotes/ko/* but changing what "+" means to something new will simply not fly. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html