On 16 May 2005 17:42:27 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> Thomas Kühne <thomas-subervsion@kuehne.cn> writes:
> > feature:
> > Extend svnadmin's dump command to support remote repositories(https,
> > http, svn, etc.).
> >
> > situation:
> > A subversion user with read and write access to a remote subversion
> > repository has no user account(e.g. ssh) on the server hosting the
> > repository.
> >
> > impacts:
> > 1) As far as I'm aware there are no protocol changes/extendsions required.
> >
> > 2) Cleaner security seperation: project members can backup the
> > repository without requiering a user account on the server.
>
> Or rather, just add an 'svn dump' command :-).
>
> I'm +1 on it. It'll happen a lot faster with a patch, of course!
>
> I think we'd want a pre-dump-hook, so that the repository has the
> opportunity to deny clients such a resource-intensive operation.
>
> Do you feel like implementing it? If so, please mail dev@ list...
I don't want to be the one who blocks all new ideas here, but can we
please have a design discussion, before even mentioning the word
'patch'? This is one of those occasions where a new contributer will
become very frustrated if he/she actually writes the patch and that
discussion will be had after patch submission.
Thanks!
Thomas, if you do feel like implementing this feature, dev@ is where
this discussion should take place, so, the request still stands :-)
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 17 12:57:55 2005