Linus Torvalds <[EMAIL PROTECTED]> writes: > On Mon, 11 Jul 2005, Eric W. Biederman wrote: >> >> 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. > > It does. It gets all the history necessary for each branch. git-rev-list > will walk the whole history until it hits commits that as been marked as > uninteresting (or the parents of commits that have been marked as > uninteresting), and those are the ones that the receiver already has, of > course.
Ok. So the intention is sane then. Looking closer it appears that commit_list_insert is recursive and that is what I missed. > So after you get a pack, you have all the history for all the branches you > got. > > A branch you _didn't_ get, you don't get any history for, of course, but > that doesn't matter. You'll get that history if you ever pull the branch > later. Right. Things work well if you have all of the history. 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
