Re: What to expect after 0.99.8

From: Junio C Hamano <junkio@cox.net>
Date: Oct 3, 2005, 21:00 UTC
Message-ID: <7vmzlqnwmw.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0510031522590.23242@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

> Are these all before 1.0, or are some of them supposed to happen 
> eventually but later?

The latter.

Show 7 quoted lines

>> * Libification.  There are many places "run once" mentality is
>>   ingrained in the management of basic data structures, which
>>   need to be fixed.
>
> I think this should be a post-1.0 thing; I think after 1.0, we should 
> rearrange a lot of the code to make more sense from a programmer 
> perspective.

I agree.

Show 6 quoted lines

>> * Look at libified GNU diff CVS seems to use, or libxdiff.
>
> I've almost got a suffix-tree-based diff that works reasonably well, 
> that's built as a library, and outputs unified diff. I need to merge it 
> with git, hook up input from trees and blobs, and test it on a wider set 
> of data.

Sounds like fun.

Show 6 quoted lines

> I'd also like to add:
>
>  * Accept patches to fetch multiple objects by HTTP in parallel.
>
> I think this may be necessary to get good performance without rsync for 
> repositories hosted without specific git support.

Surely. I'd love to see you work with Nick Hengeveld on this one, perhaps even before 1.0. Looking out the fetch.c code, I think you already have set up a reasonable "work queue" during the last round, with a lot of simplification thanks to Sergey, and parallel fetching would be a very nice addition.