Jordan DE GEA <jordan.de-...@grenoble-inp.org> writes: > Here is what we want to implement:
Your message contains the word "implement" too many times. Before thinking about implementation, think, and discuss, about the design. If your message is intended to be a discussion on the design, then avoid using "implementation" in the subject. > 1. > a. add the config var: remote.fetchDefault > b. add the config var: branch.<name>.fetchRemote > c. add `git fetch --set-default` in order to set remote.fetchDefault > d. add `git fetch --set-remote` in order to set > branch.<name>.fetchRemote > e. add `git pull --set-default` in order to set remote.fetchDefault > f. add `git pull --set-remote` in order to set branch.<name>.fetchRemote > > 2. > a. add `git push --set-default` in order to set remote.pushDefault > b. add `git push --set-remote` in order to set branch.<name>.pushRemote This tells a lot about the "what?", but lacks the most important "why?" (or "what for?") question. The user doesn't want to "set configuration variables". He wants to work with git, have commands do the right thing, avoid typing useless keystrokes and avoid surprising behavior. Please explain how your proposal would improve the situation. For example, show a typical use-case with commands to type before and after your proposal is implemented. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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
