It's just that when I attempt to run svn import, it calls for start commit.
How can I stop this from happening?
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Thursday, July 08, 2004 1:39 PM
To: Griffin, Nicole; users@subversion.tigris.org
Subject: RE: svn import Problem
[Please keep this on the list]
On Thu, 2004-07-08 at 12:30, Griffin, Nicole (Newport News) wrote:
> I basically just took off the comment lines of the start-commit.tpml
> (using the original format of the script). The template called for
> those scripts. I wasn't sure if I had to actually write two scripts
> that checked the user's credentials or if I could just use the ones in
> the template. I guess this means I have to write scripts to do this
> tasks. Thanks.
I don't understand: what do you want to do? I hope you understand that you
don't *need* a start-commit hook at all to function.
On the other hand, if you want some sort of access control, I suggest you
read chapter 6. Hook scripts are only one way of achieving that.
svnserve and apache have their own authorization systems as well. You
probably don't want to reinvent your own authorization system.
To answer your original question: yes, the two scripts in the start-commit
template are fictitious. They're only there to show an example of how one
would pass arguments to an external authorization script.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 8 20:04:00 2004