Re: builtin-fetch code with messy history

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 19, 2007, 09:40 UTC
Message-ID: <Pine.LNX.4.64.0706191037590.4059@racer.site>
In-Reply-To: <Pine.LNX.4.64.0706190255430.4740@iabervon.org>

Hi,

On Tue, 19 Jun 2007, Daniel Barkalow wrote:

Show 6 quoted lines

> In my branch at: git://iabervon.org/~barkalow/git builtin-fetch
> 
> I have a bunch of not-for-merging history leading up to a C version of 
> fetch which passes all of the tests except that:
> 
>  * it might be fetching too much with --depth.

That should be fixable. (If I get more time this week than I expect, I'll do it myself.)

>  * bundle isn't implemented.

That's an easy one.

>  * when a branch config file section refers to a branches/* remote, the 
>    merge setting is used (if one is given), even though this isn't useful 
>    either way.

Maybe this is the right time to cut off branches/* and remotes/*?

Show 8 quoted lines

>  * branch.<name>.merge is treated like the source side of a refspec 
>    (although it cannot be a wildcard), and it fetched refs are marked for 
>    merging if they name the same ref, even if they are not character-wise 
>    identical to the source side of the refspec used to fetch them.
> 
> I've got more work to do on it (such as actually using my parser for 
> parsing the refspecs and making the logic less convoluted), but I 
> thought I'd report my progress.

Thank you very much! Dscho