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

Re: [PATCH] git-svn: avoid respewing similar error messages for missing paths

From
EWEric Wong <normalperson@yhbt.net>
Date
Apr 2, 2007, 18:46 UTC
Message-ID
<20070402184652.GA29646@hand.yhbt.net>
In-Reply-To
<m2lkhb6pbm.fsf@gmail.com>
Seth Falcon <sethfalcon@gmail.com> wrote:
Show 9 quoted lines
> I have the impression that the initial fetch phase is taking longer
> than it used to.  This could easily be due to network and server load
> related issues, but I wonder if something in the parent following /
> path searching is different.  The first git svn fetch seems to do
> nothing for a very long time (except emit a few of the warnings) and
> then once it starts actually adding commits it goes quite fast.  This
> isn't really a problem as the initial fetch is a fairly rare
> operation, but I wondered if this made sense based on recent git-svn
> changes...
Does using --log-window-size=1000 speed things back up?

I decreased it to 100 to reduce memory usage (but exposed it as an option).

-- 
Eric Wong
Previous: Seth Falcon
Message 6 of 6 in “git svn fetch spewing warnings”
  1. Seth FalconMar 26, 2007
  2. Eric WongMar 27, 2007
  3. Seth FalconMar 27, 2007
  4. git-svn: avoid respewing similar error messages for missing pathsEric Wong, Mar 31, 2007
  5. Seth FalconApr 2, 2007
  6. Eric WongApr 2, 2007

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.