Good suggestion.
In my defense (well not really), since the decription of this project
is "same as and better than CVS" and I can make CVS do exactly what I
have decribed and need, I figured it would be easy or easier than CVS
to get Subversion to do the same tasks...
My mistake.
Thanks for your help.
On 7/20/05, Ben Collins-Sussman <sussman@collab.net> wrote:
>
> On Jul 20, 2005, at 1:58 PM, Phil wrote:
>
> > yes I want to prevent them from breaking and stealing locks yes. There
> > is a way of doing that?
>
> Yes, it's explained in the locking section of the book.
>
> >
> > Email? cool... I have not seen that feature... I can get an email when
> > a file is changed? or commited?
>
> Yes, most every project does that. It's explained in chapter 5 of
> the book, which is all about repository administration (and 'hooks',
> in this case.)
>
> It seems like you've got a very specific set of behaviors and
> features in your mind, and want Subversion to conform to them. As
> someone said already, that might not always be possible. A better
> strategy might be to sit down with a nice cup of tea, and spend an
> afternoon reading the book straight through. I get the impression
> that you've not yet done this, that you aren't really aware of what
> Subversion is capable of. (You keep sending mails asking "How do I
> make subversion do X? And Y? and Z"?)
>
> You may have to change your processes to adapt to Subversion, rather
> than the other way around.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 20 21:47:10 2005