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

"git svn mkdirs" is very slow

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Mar 28, 2011, 15:05 UTC
Message-ID
<4D90A3AA.3050601@alum.mit.edu>
Hello,

I've noticed that in our repository, "git svn mkdirs" or any other command that calls mkemptydirs() is very slow (approximately 8.5 s even with a warm disk cache). Presumably this is related to the fact that the unhandled.log.gz for our Subversion trunk is almost 10 Mb.

Of course it would be nice if this were faster.

But we have laid out our repository to make the presence/absence of empty directories irrelevant, so we would be just as happy if git-svn would *not* create empty directories, like in the good old days. So I wanted to implement the following feature:

1. An svn.autoMkdirs / svn-remote.<name>.autoMkdirs configuration
variable.  The value should default to true for backwards compatibility.
2. Only call mkemptydirs() if this variable is set to true.
3. Make an exception for "git svn mkdirs", which should do its thing
regardless of how this configuration option is set.

I think it should only be about a 10-line change, plus documentation and tests. Unfortunately, my perl-foo is very limited, and it will take me a while to figure out how option parsing and handling works in git-svn.

Would this feature be welcome?

Is there anybody willing to make the Perl changes? I would be willing to work on the documentation and test suite changes.

Thanks, Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Next: Junio C Hamano
Message 1 of 3 in “"git svn mkdirs" is very slow”
  1. Michael HaggertyMar 28, 2011
  2. Junio C HamanoMar 28, 2011
  3. git-svn: add an option to skip the creation of empty directoriesMichael Haggerty, Apr 1, 2011

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.