Mark Rushakoff <mark@xxxxxxxxxxxxxx> writes: > I have a shallow clone of a repository. Then sometime later, I obtain a bundle > containing full history. > > I thought I could use git fetch --unshallow /path/to/repo.bundle > mybranch:mybranch, but I've found that git does not support shallow fetches > from a bundle and that unshallow is actually an alias for --depth=2147483647 in > 4dcb167fc3 (fetch: add --unshallow for turning shallow repo into complete one, > 2013-01-11). > > If I do a plain fetch from the bundle, I can manually modify .git/shallow to > "unshallow" my repository like the previous email in this thread. But what I > think I still want here is a way to tell git "here are all the objects I have; > update the shallow boundaries accordingly." It sounds like a quite sensible request to me. Offhand, I do not think of anything that would make it fundamentally impossible to allow us to first add objects to the .git/objects directory by whatever means available to you (including, but not limited to, exploding the object data from a full bundle) and then to tell Git to see if there (still) are missing commits and objects that ought to exist but don't that necessitates the repository to be marked "shallow", and adjust the boundary. I however do not think there is such a code already written X-<.
