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

Re: git svn fetch spewing warnings

From
Seth Falcon <sethfalcon@gmail.com>
Date
Mar 27, 2007, 19:17 UTC
Message-ID
<m23b3qts11.fsf@ziti.fhcrc.org>
In-Reply-To
<20070327190004.GD16591@localdomain>
Eric Wong <normalperson@yhbt.net> writes:
> We now try harder to find previous versions of the path we're tracking.
> I've also changed the window from 1000 to 100 revisions, so the
> warning message spewing is 10 times more frequent.  Don't worry, though
> it's harmless :)

Not a big deal. But perhaps those warnings could go to a log file of some kind and then a summary at the end could say:

  There were 500 warning messages, check git-svn-fetch-TIMESTAMP.log
  for details.

And to push a bit further, why do I care about these messages. What action might I take based on them? I almost didn't discover that the warnings were harmless because I C-c'd out a few times thinking that something was really wrong before deciding to just let it run.

+ seth
-- 
Seth Falcon
Previous: Eric WongNext: Eric Wong
Message 3 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.