Ramkumar Ramachandra wrote: > Dmitry Ivankov writes: >> Hm, I don't see much differences. >> Data format is the same SVN-fs-dump-format-version: 3. In my case I >> observe following differences: >> - svnadmin writes sha1 checksums along with md5 ones >> - hashtable dumps can have different elements dump order >> - svnrdump sets Prop-delta: true for empty props >> - text deltas can be encoded differently (does it affect svn:ann?) >> My svnadmin is version 1.6.16 (r1073529) >> svnrdump is from r1135490 >> >> Anything else I'm missing in a simple dump of a repository root? > > Yes, those are the differences. Are the differences documented somewhere (e.g., the svnbook)? >>> I saw this '--username', '--password' in other patches too. I'm >>> probably missing context, but I'm curious to know why this is required >>> and what you're planning to do to fix it in the future. [...] >> It's a placeholder for quick local patch if anyone wants to test a >> repo with permissions. I suspect it snuck in from tests with the cvs2svn repository. :) Do you know another small repository that's entertaining to test with? >> In future it should be allowed to configure credentials in >> corresponding remote section of git.config Yep, something along those lines sounds sensible. In the short term, I think there's been some talk of a configuration option to override the svnrdump command; that could be used to pass credentials. Inspired by the old HTTP convention, I tried svn log http://Guest:@cvs2svn.tigris.org/svn/cvs2svn and svn log http://Guest:pass@xxxxxxxxxxxxxxxxxx/svn/cvs2svn but alas, neither works. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html