git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
EWEric Wong <normalperson@yhbt.net>
Date
Feb 17, 2010, 23:23 UTC
Message-ID
<20100217232342.GA29610@dcvr.yhbt.net>
In-Reply-To
<94a51d821002161717q4dd116f9tebff3a2475446a8e@mail.gmail.com>
Robert Zeh <robert.allan.zeh@gmail.com> wrote:
Show 27 quoted lines
> 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
Previous: Robert Zeh
Message 2 of 2 in “Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)”
  1. Robert ZehFeb 17, 2010
  2. Eric WongFeb 17, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.