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

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

## Robert Zeh, 2010-02-17 01:17

Subject: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Message-ID: <94a51d821002161717q4dd116f9tebff3a2475446a8e@mail.gmail.com>
URL: https://gitlist.dev/e/94a51d821002161717q4dd116f9tebff3a2475446a8e%40mail.gmail.com

```
Since upgrading from 1.6.5.2 to 1.7.0 I've noticed a change in how
git svn fetches from the Subversion repository on tags.  Of course,
for the repo I'm working with there are many more tags then branches.
1.6.5.2 gives me the following on a tag:


r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)
Found possible branch point:http://bt011us013s/prod_repos/trunk
=>http://bt011us013s/prod_repos/tags/3.09.1255, 333
Found branch parent: (refs/remotes/tags/3.09.1255)
b15f3f20710a1e282fb6ff62c13fad64376ad2b4
Following parent with do_switch
Successfully followed parent

r334 = 77d132d69bc333e7c988a4f3af9d48a98dadf0d4 (refs/remotes/tags/3.09.1255)

With 1.7.0:
r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)

        A       Enterprise/Header.txt
        ....

r334 = 2c0e6dd89e81e7d18288e135f40f193b2ff22018 (refs/remotes/tags/3.09.1255)

The SHA1s are also different.

It would be nice if the entire branch wasn't fetched.

Robert

```

## Eric Wong, 2010-02-17 23:23

Subject: Re: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Message-ID: <20100217232342.GA29610@dcvr.yhbt.net>
URL: https://gitlist.dev/e/20100217232342.GA29610%40dcvr.yhbt.net
In-Reply-To: <94a51d821002161717q4dd116f9tebff3a2475446a8e@mail.gmail.com>

```
Robert Zeh <robert.allan.zeh@gmail.com> wrote:
> Since upgrading from 1.6.5.2 to 1.7.0 I've noticed a change in how
> git svn fetches from the Subversion repository on tags.  Of course,
> for the repo I'm working with there are many more tags then branches.
> 1.6.5.2 gives me the following on a tag:
> 
> 
> r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)
> Found possible branch point:http://bt011us013s/prod_repos/trunk
> =>http://bt011us013s/prod_repos/tags/3.09.1255, 333
> Found branch parent: (refs/remotes/tags/3.09.1255)
> b15f3f20710a1e282fb6ff62c13fad64376ad2b4
> Following parent with do_switch
> Successfully followed parent
> 
> r334 = 77d132d69bc333e7c988a4f3af9d48a98dadf0d4 (refs/remotes/tags/3.09.1255)
> 
> With 1.7.0:
> r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)
> 
>         A       Enterprise/Header.txt
>         ....
> 
> r334 = 2c0e6dd89e81e7d18288e135f40f193b2ff22018 (refs/remotes/tags/3.09.1255)
> 
> The SHA1s are also different.
> 
> It would be nice if the entire branch wasn't fetched.

Hi Robert,

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.

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

-- 
Eric Wong

```