git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Dmitry Ivankov <divanorama@gmail.com>,
	git@vger.kernel.org, David Barr <davidbarr@google.com>
Subject: Re: [PATCH 2/5] svn-fe: allow svnadmin instead of svnrdump in svn helper
Date: Wed, 6 Jul 2011 06:28:17 -0500	[thread overview]
Message-ID: <20110706112817.GN15682@elie> (raw)
In-Reply-To: <CALkWK0=UKvvVVeRKcMq1L5ywV0WcAn4BNvEeQuTTZtZAmubanA@mail.gmail.com>

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@cvs2svn.tigris.org/svn/cvs2svn

but alas, neither works.

  reply	other threads:[~2011-07-06 11:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 16:45 [PATCH 0/5] remote-svn-alpha updates Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 1/5] svn-fe: use svnrdump --quiet in remote-svn-alpha Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 2/5] svn-fe: allow svnadmin instead of svnrdump in svn helper Dmitry Ivankov
2011-07-06 10:12   ` Ramkumar Ramachandra
2011-07-06 11:02     ` Dmitry Ivankov
2011-07-06 11:11       ` Ramkumar Ramachandra
2011-07-06 11:28         ` Jonathan Nieder [this message]
2011-07-05 16:45 ` [PATCH 3/5] svn-fe: add a test for remote-svn-alpha Dmitry Ivankov
2011-07-05 16:45 ` [PATCH 4/5] svn-fe: use svn-fe --no-progress in remote-svn-alpha Dmitry Ivankov
2011-07-06  9:56   ` Ramkumar Ramachandra
2011-07-06 12:30     ` Jonathan Nieder
2011-07-05 16:45 ` [PATCH 5/5] svn-fe: use proper refspec " Dmitry Ivankov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110706112817.GN15682@elie \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=davidbarr@google.com \
    --cc=divanorama@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).