On Fri, Feb 08, 2008 at 05:44:12PM +1300, Martin Langhoff wrote:Thinking about this more, this situation is more than a minor annoyance: it is actually somewhat dangerous. If you ever wanted to push _one_ non-ff case (say, for your current branch) and you were to use "git push -f", you would rewind history for random branches, and sorting the mess out at the remote could be awful (especially if it is a bare repo without reflogs). I really think that Steffen's "default to pushing only the current branch" approach fits much better with the model described in your workflow, and is generally a safer default. IIRC, the main objection was that old-timers like the current push behavior better. Steffen, was there objection to a "push.onlyHEAD" config option? -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
| Davide Libenzi | [patch 7/8] fdmap v2 - implement sys_socket2 |
| Greg Kroah-Hartman | [PATCH 018/196] coda: convert struct class_device to struct device |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| David Newall | Re: Slow DOWN, please!!! |
git: | |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
