Linus Torvalds <[EMAIL PROTECTED]> writes: > On Mon, 11 Jul 2005, Eric W. Biederman wrote: >> > So if you only get one branch, it will leave the objects that are specific >> > to other branches alone. >> >> Hmm. As I recall reading the code it grabs everything that is >> in .git/refs/*. > > Only by default. > > If you specify a branch (or five) git-clone-pack will grab only that > branch. > > However, I don't think "git clone" (the script) even exposes that, so > right now you'd not even see it - "git clone" only exposes the "get all > the branches by default" behaviour.
Yep. The question: Does git-upload-pack which gets it's list of objects with "git-rev-list --objects needed1 needed2 needed3 ^has1 ^has2 ^has3" get any history beyond the top of tree of each branch. As I read the code it does not. If the code does not get the history I see some problems. In particular merging with a branch is hard because we may not pull the common history point. Eric - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
