Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:It's not that "exactly" for me. If your push were "next~27^2:frotz", it becomes even less clear. It may be that I am pushing out the tip of a topic branch I usually do not push out, so it would be easier for some specific person to build on top of. Or maybe I am marking that place as a lightweight tag. They are equally likely. On the other hand, what the user wants to do with "git push $elsewhere frob" is reasonably clear. If frob is locally a branch, then the branch is pushed out. If frob is a tag, the tag is propagated. - 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
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 025/196] paride: Convert from class_device to device for block/paride |
| Henrique de Moraes Holschuh | [RFC] rfkill class rework |
git: | |
| Gerrit Renker | [PATCH 05/37] dccp: Cleanup routines for feature negotiation |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Johann Baudy | Packet mmap: TX RING and zero copy |
| David Miller | [GIT]: Networking |
