Re: Clone from shallow bundle bug

[Phillip Susi <psusi@ubuntu.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 04/01/2015 08:33 PM, Duy Nguyen wrote:
> OK two additional options on top of what we already have:
> 
> - save .have and add extra prerequisite SHA-1. - create a bundle
> that does not hit shallow boundary in the first place, roughly
> speaking it's "max depth minus one". This one does not have extra
> .have or prerequisites

Huh?  If it is one less deep that doesn't help: the new clone will
still be missing history.  AFAICS, the only way to keep the new clone
kosher is for it to have a .git/shallow file that identifies it as a
shallow clone so that history walks stop short instead of complaining
about the missing history.

Thus, all that is needed is for the clone, when it notices that
history is missing, is to create the shallow file instead of erroring
out, telling you to fsck yourself, and rudely deleting the new clone.
 It is one thing to tell you that there is missing history, but quite
another to delete the repository it just created due to it missing
history.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCgAGBQJVHJraAAoJENRVrw2cjl5RABEH/RW+J5eFNRL80qMVSSnYI4Wb
RjCb5Lb1pp4PBQtGK6yJ/7lzDYptAN6aLcpMVrGiyIIJDm7KfZ6rGvhUegn37ImH
dCelZs+XHeR1dVd05Lbn9FGgB3mg873JOb5+i/hMuuudrXhNjRy6hhFGBnVulpPP
lySfaPMscbSH7lzqr1zxgdu4GzRLlLPzKv1ojiWGyy97iRAsN6bRy6I1/wsddKMn
hESUlv7AdTNQxu3b3NsLGS20a9QHMpKjBxBLvOYE6ftr4yyHMkxum/+BnoASY2UB
h5LenKnQzRwFNGiw1BDeQESqYDXpQ4yA7lpd91gsINwgVsRqg82iSen9/fszzq0=
=shT5
-----END PGP SIGNATURE-----