On Fri, Feb 08, 2008 at 07:24:06PM -0800, Junio C Hamano wrote:Not necessarily; you might not even have the refs that you just rewound. I think only that: - it's more typing, so if there is a class of users who want to use "git push origin HEAD" as their workflow, it might make sense to support them with a config option - I have seen less experienced users expecting "git push" to do a single branch (i.e., users whose workflow is "git pull; hack hack hack; git push"). With one branch it is not a problem, but as soon as you introduce them to other branches, then the push behavior is yet another thing that you have to explain. And I know "clueless users" is not a good reason to change defaults if it makes clueful users less happy, but it might be reason for a config option. Ah, I forgot about that. Yes, that does work in 1.5.4. I have often wanted that, since I typically only _ever_ push to an origin, but the DWIM made me paranoid that it could be unsafe. If you had a remote and a branch name that were similar, then a typo could end up pushing to the wrong place. -Peff - 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
| Greg Kroah-Hartman | [PATCH 012/196] nozomi driver |
| Ingo Molnar | Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 |
| Rafael J. Wysocki | [PATCH -mm 5/6] Freezer: Remove PF_NOFREEZE from bluetooth threads |
| Ingo Molnar | Re: [PATCH 00/23] per device dirty throttling -v8 |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Natalie Protasevich | [BUG] New Kernel Bugs |
