Yesterday I created a git bundle as best as I can remember like this git bundle save chunk chunk.bundle --all master Note the 'master' I added accidentally at the end - this was a user error but still the bundle was created. When I tried to clone this, I get ~\local\src> git clone 'G:\My Drive\chunk.bundle' fs2-columns Cloning into 'fs2-columns'... Receiving objects: 100% (31/31), done. Resolving deltas: 100% (5/5), done. fatal: multiple updates for ref 'refs/remotes/origin/master' not allowed. ~\local\src> git bundle verify chunk.bundle The bundle contains these 3 refs: 3c804437a5f8537db1bfb5d09b7bff4f9950605e refs/heads/master 3c804437a5f8537db1bfb5d09b7bff4f9950605e HEAD 3c804437a5f8537db1bfb5d09b7bff4f9950605e refs/heads/master The bundle records a complete history. chunk.bundle is okay After trying a couple of things, I finally managed to clone it using ~\local\src> git clone -b master --single-branch .\chunk.bundle fs2-columns i.e. the '--single-branch' option saved me. Is this a bug? Should bundle allow providing multiple refspecs when `--all` is provided? I admit this was clearly a case of 'caveat emptor', but shouldn't this be disallowed (i.e. is there any situation when this is useful?) Thanks! Luciano -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of the Dinosaur Group. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.