# Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)

3 messages from 2010-02-17 to 2010-02-19. Participants: Robert Zeh, Eric Wong.
Thread: https://gitlist.dev/t/22701

## Robert Zeh, 2010-02-17 23:54

Subject: Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Message-ID: <5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF@gmail.com>
URL: https://gitlist.dev/e/5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF%40gmail.com

```
On Feb 17, 2010, at 5:23 PM, Eric Wong <normalperson@yhbt.net> wrote:
> There was a rather large amount of changes between 1.6.5.2 so some
> regressions could've slipped in.  A bisection would definitely help
> us track down the cause.

I will attempt a bisection Thursday.

>
> Does the repository you're using svn:mergeinfo use by any chance?

The repository does use mergeinfo, but    much later in the revision  
history then when the problem shows up.

Do you have any advice on how to write a test for this behaviour,  
since the problem is not apparent from looking at the repo?  I do not  
like the idea of a test looking at a log but that is all I can think  
of right now.

Robert

```

## Eric Wong, 2010-02-18 00:06

Subject: Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Message-ID: <20100218000620.GA7123@dcvr.yhbt.net>
URL: https://gitlist.dev/e/20100218000620.GA7123%40dcvr.yhbt.net
In-Reply-To: <5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF@gmail.com>

```
Robert Zeh <robert.allan.zeh@gmail.com> wrote:
> On Feb 17, 2010, at 5:23 PM, Eric Wong <normalperson@yhbt.net> wrote:
>> There was a rather large amount of changes between 1.6.5.2 so some
>> regressions could've slipped in.  A bisection would definitely help
>> us track down the cause.
>
> I will attempt a bisection Thursday.

Awesome, thanks.

>> Does the repository you're using svn:mergeinfo use by any chance?
>
> The repository does use mergeinfo, but    much later in the revision  
> history then when the problem shows up.
>
> Do you have any advice on how to write a test for this behaviour, since 
> the problem is not apparent from looking at the repo?  I do not like the 
> idea of a test looking at a log but that is all I can think of right now.

Andrew and Sam are the people to ask about mergeinfo, but I've found
reading logs valuable for tracking down many issues in the past.

I'm not 100% convinced mergeinfo itself is the problem (but it's the
code I'm least familiar with), and there were also some changes with
globbing (which I believe were harmless improvements).

-- 
Eric Wong

```

## Robert Zeh, 2010-02-19 12:14

Subject: Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Message-ID: <F3657B42-F723-4656-A86E-3117B355D6C0@gmail.com>
URL: https://gitlist.dev/e/F3657B42-F723-4656-A86E-3117B355D6C0%40gmail.com
In-Reply-To: <20100218000620.GA7123@dcvr.yhbt.net>

```

On Feb 17, 2010, at 6:06 PM, Eric Wong <normalperson@yhbt.net> wrote:

> Robert Zeh <robert.allan.zeh@gmail.com> wrote:
>> On Feb 17, 2010, at 5:23 PM, Eric Wong <normalperson@yhbt.net> wrote:
>>> There was a rather large amount of changes between 1.6.5.2 so some
>>> regressions could've slipped in.  A bisection would definitely help
>>> us track down the cause.
>>
>> I will attempt a bisection Thursday.
>
> Awesome, thanks.

I now believe the real problem is that I had an ignore-paths set in  
the repo that fetched the entire trunk on branch.  Is this expected?

Robert
>

```
