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 18, 2010, 00:06 UTC
Message-ID
<20100218000620.GA7123@dcvr.yhbt.net>
In-Reply-To
<5CFEDDA0-6C6B-43DF-8BB4-E303E91C24EF@gmail.com>
Robert Zeh <robert.allan.zeh@gmail.com> wrote:
Show 6 quoted lines
> 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.
Show 8 quoted lines
>> 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
Previous: Robert ZehNext: Robert Zeh
Message 2 of 3 in “Re: 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 18, 2010
  3. Robert ZehFeb 19, 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.