Never having needed git bundle before, I've recently been using it as a sneakernet. In particular, I'm using bundles to work around limitations of filesystem semantics on vfat and hpfs+ drives when shared between Linux and OS X systems. The systems are air-gapped, so sneakernet is essential. At any rate, the issue I'm dealing with is that "git bundle unbundle" is sort of non-intuitive to deal with. It seems to add the commits directly to the local repository, but doesn't give me any of the branch refs that I'm expecting from such an operation. In other words, if I bundle branch foo on machine A, then unbundle on machine B, I expect to be able to "git checkout foo" and get on with life. Instead, it seems that I have to figure out what commits were unbundled, and create a new branch ref pointing to the head that I want. I assume this is to prevent namespace collisions, but it seems really, really cumbersome. Wouldn't it make more sense to include branch names in the bundle, and simply prompt the user to rename refs that conflict? I'm certainly open to other ideas of how to accomplish this workflow, and if there's an invocation to simplify this that I'm unaware of, please advise. Otherwise, I really think the default behavior of the unbundle sub-command ought to be more intuitive. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html