Re: [PATCH] Fix fetch completeness assumptions
- From
Junio C Hamano <junkio@cox.net>
- Date
- Sep 15, 2005, 08:09 UTC
- Message-ID
- <7vd5naah1m.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.63.0509142120020.23242@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
Show 10 quoted lines
> Don't assume that any commit we have is complete; assume that any ref > we have is complete. > > Signed-off-by: Daniel Barkalow <barkalow@iabervon.org> > > --- > Only lightly tested, but it seems to work. Marks all of the commits in > refs, and their ancestors back as far as the date of the commit it's > processing. If the commit it's processing is marked, it doesn't recurse > into it.
First I thought you were using the date for the cutting-off decision and was going to object to the patch because of it, but re-reading the code made me realize that you are using date only to better the heuristics that limits how many commits reachable from existing refs we would tangle to see if the newly seen commit is reachable from our refs -- the logic looks correct.
The "complete" commit_list is a clever piece of code; I like it.