On Oct 24, 2007, at 11:28 PM, Peter Baumann wrote:You're not forced to pull. Just use "git fetch" if you want to do this. Or is something missing if you'd be limited to "git fetch"? I (and, as I understood, Andreas, too) want to change the default. Because we believe that git would be easier to use in workflows based on a shared repository. But if we fail to convince the list, maybe a global configuration variable that configures "git pull" to autoforward branches as propose would be a nearly equally good solution. However, I think it is dangerous to introduce many of such configuration options. Explaining the behaviour of git will become harder. The behaviour will become dependent on the local configuration and eventually the first question before answering a question will be "send me the output of 'git config --list'. I need to see how your git is configured." Steffen - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Kamalesh Babulal | [BUILD-FAILURE] 2.6.26-rc8-mm1 - build failure at drivers/char/hvc_rtas.c |
| Luciano Rocha | usb hdd problems with 2.6.27.2 |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
git: | |
