-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/1/2015 5:55 AM, Duy Nguyen wrote: > On Wed, Apr 1, 2015 at 4:10 AM, Phillip Susi <psusi@xxxxxxxxxx> > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> I made a shallow clone of my repo, then used git bundle create to >> pack it all into a bundle file, then cloned from that bundle. >> The initial shallow clone has a .git/shallow file that identifies >> it as a shallow clone ( and I guess keeps things from complaining >> about the missing history ), but the the repo cloned from the >> bundle does not, > > You made me worry a bit. We have checks in clone and fetch to make > sure the result is "good" (i.e. gitk should not complain, > clone/fetch should report it instead). Unfortunately I tested and > it seemed to work as expected (i.e. clone fails) > > $ LANG=C ./git clone ./shallow.bundle shallow2 Cloning into > 'shallow2'... Receiving objects: 100% (2813/2813), 5.33 MiB | 0 > bytes/s, done. Resolving deltas: 100% (250/250), done. Checking > connectivity... error: Could not read > 50a3ba22454e2989424d5de489de9c0f68fed5ec fatal: Failed to traverse > parents of commit c73a8a63134734ddf7077d09355a10a0077ed2ca fatal: > remote did not send all necessary objects Strange; it works fine for me using git 1.9.4.msysgit.1, and then I just get the complaints from gitk. I created the bundle with no prereq argument, i.e. "git bundle create shallow.bundle". Did you use a prereq argument? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJVG+pKAAoJENRVrw2cjl5RLkMH/j0IlFsf5oEsFejLqD2fxFAJ 8r7pZCtYFvFqMqLQivLCdU/aYCd/5F99VUtusH3NphJvxkmCaLyRwLyA1KR/AozQ slEXc5gmjbUg9yEBffYQ/xFPAGrizb2BblSzl6hcAZGtscLNyKvOjHttvJL+xM1+ uY0dwHcQ97m5p3DlehjLSAHolJF+waEhS6MarACZuSbi2JBTvo3OOagyt0o46sjp t5v4kfRfTYD6DTlY+VPTUC56unBaVItLDfxY5d+iHGDY2o5rhl4AFWLbCh3v6ltl OAuVs+UPKn0kV9tIQ6EBhQKf5CooCZtbr45OVGpVLPipjQFq2QqUjVWrLMEskhw= =Fem/ -----END PGP SIGNATURE----- -- 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