[PATCH 0/4] The rest of builtin-fetch

[PATCH 0/4] The rest of builtin-fetch

[Daniel Barkalow]

This series is the rest of builtin-fetch. It should probably not be used 
without a "[PATCH 3.5/4] Support bundles in transport fetch" which 
Johannes was going to write.

The first patch of this is independant of anything else, but the rest 
depend on all of the other series I have sent recently. One thing I 
already plan to fix while doing revisions for comments is that the 
"remote.<name>.tagopt" config variable parsing is added by the second 
patch, when it would be more logically added by the first.

When the development cycle is at the right point for getting all this in, 
I'll be sending out the complete set of patches (aside from the pair that 
were already accepted). I'm also going to send out another revision of 
builtin-fetch-pack.c that adds a bit of memory freeing and depends on the 
first of the accepted pair. And I've got a builtin-send-pack (with a 
function for transport.c to call directly), although that's not in the 
critical path.

	-Daniel
*This .sig left intentionally blank*

Re: [PATCH 0/4] The rest of builtin-fetch

[Johannes Schindelin]

Hi,

On Wed, 11 Jul 2007, Daniel Barkalow wrote:

> This series is the rest of builtin-fetch. It should probably not be used 
> without a "[PATCH 3.5/4] Support bundles in transport fetch" which 
> Johannes was going to write.

8-)

It is 3am, and I am already in the middle of git hacking, and should go to 
bed, so that'll have to wait for tomorrow...

Ciao,
Dscho

Re: [PATCH 0/4] The rest of builtin-fetch

[Daniel Barkalow]

On Thu, 12 Jul 2007, Johannes Schindelin wrote:

> Hi,
> 
> On Wed, 11 Jul 2007, Daniel Barkalow wrote:
> 
> > This series is the rest of builtin-fetch. It should probably not be used 
> > without a "[PATCH 3.5/4] Support bundles in transport fetch" which 
> > Johannes was going to write.
> 
> 8-)
> 
> It is 3am, and I am already in the middle of git hacking, and should go to 
> bed, so that'll have to wait for tomorrow...

We're presumably waiting for 1.5.3 before this actually goes anywhere, so 
there's no big hurry. Just don't want it to get forgotten and have 
mainline versions where the tests don't pass due to bundles not working 
(or, worse, an actual release where we forget about them in this context).

	-Daniel
*This .sig left intentionally blank*