You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Romain Prévost <pr...@gmail.com> on 2005/07/20 15:43:25 UTC
Documentation about the 'Lock' feature
Hi,
I'd like to learn how to use and setup my server to be able to use
locks, but I can't find any documentation in the SVN book. Can someone
give me more information ?
Thanks a lot.
--
Romain Prévost
Epitech promotion 2007
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jul 20, 2005, at 10:43 AM, Romain Prévost wrote:
> Hi,
>
> I'd like to learn how to use and setup my server to be able to use
> locks, but I can't find any documentation in the SVN book. Can someone
> give me more information ?
Look at the svn 1.2 book on http://svnbook.red-bean.com, it's all in
chapter 7.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
And by that I mean changing svn:needs-lock and other properties...
On 7/20/05, Phil <pl...@gmail.com> wrote:
> yes I want to disable all concurrency...
>
> And on that note, how can I disable users from changing file
> properties in subversion... I mean if I give a user write access can
> they change the files properties?
>
>
>
>
> On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
> >
> > On Jul 20, 2005, at 1:29 PM, Phil wrote:
> >
> > > I did and this is what I am try to issue:
> > >
> > > svn propset svn:needs-lock * reponame
> > >
> > > does nto work...?
> > >
> > > I need specific help... what specifically do I need to issue as a
> > > command to set the property to all the subdirectories below my
> > > repository that I have called 'reponame'?
> > >
> > > everything I tried gives me the error:
> > > '.' is not a working copy
> > >
> >
> > You can only lock files, not directories. Therefore, it only makes
> > sense to set 'svn:lock' property on files.
> >
> > It sounds, then, like you want to run 'svn propset' on every file in
> > your working copy. To do this, use your shell, or write a simple
> > script of some sort.
> >
> > (Are you really certain that you want to completely disable
> > concurrency on the whole project? You want to force people to lock
> > *every* file before they begin editing?)
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Documentation about the 'Lock' feature
Posted by Erik Anderson <er...@teamworkgroup.com>.
If some of your developers are "less trustworthy" than others, maybe you
want to give them their own branch to play with. That way any
"unauthorized changes" stay on the branch and are not merged upwards.
Otherwise there should be a log of the changes made to a file. If someone
changed a file property, you should be able to figure out who it was and
when it was changed.
-----Original Message-----
From: Phil [mailto:plabonte@gmail.com]
Sent: Wednesday, July 20, 2005 11:59 AM
To: Ben Collins-Sussman
Cc: Patrick Burleson; David Weintraub; Romain Prévost; mailinglist
subversion users
Subject: Re: Documentation about the 'Lock' feature
yes I want to prevent them from breaking and stealing locks yes. There
is a way of doing that?
Email? cool... I have not seen that feature... I can get an email when
a file is changed? or commited?
Yes well I have found if you provide the developpers an inch they will
take a mile and the higher ups are developpers too and they do not
give them any sh#t when they screw up, it is usally blamed on me for
giving them too much access...
On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
>
> On Jul 20, 2005, at 1:42 PM, Phil wrote:
>
> > yes I want to disable all concurrency...
> >
> > And on that note, how can I disable users from changing file
> > properties in subversion... I mean if I give a user write access can
> > they change the files properties?
> >
> >
>
> Yes, they can, and there's no way to stop them. Either they have
> write access to the file (can commit changes to a file's text and
> properties), or they don't have write access to the file (they cannot
> commit any changes to text or properties.)
>
> It sounds like you're trying to "control developers with an iron
> fist". If they change a property, wouldn't you see an email saying
> so, and wouldn't you scold the user?
>
> (Are you also planning to prevent users from breaking and stealing
> locks?)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
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 <su...@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
Re: Documentation about the 'Lock' feature
Posted by Ben Collins-Sussman <su...@collab.net>.
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
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
yes I want to prevent them from breaking and stealing locks yes. There
is a way of doing that?
Email? cool... I have not seen that feature... I can get an email when
a file is changed? or commited?
Yes well I have found if you provide the developpers an inch they will
take a mile and the higher ups are developpers too and they do not
give them any sh#t when they screw up, it is usally blamed on me for
giving them too much access...
On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
>
> On Jul 20, 2005, at 1:42 PM, Phil wrote:
>
> > yes I want to disable all concurrency...
> >
> > And on that note, how can I disable users from changing file
> > properties in subversion... I mean if I give a user write access can
> > they change the files properties?
> >
> >
>
> Yes, they can, and there's no way to stop them. Either they have
> write access to the file (can commit changes to a file's text and
> properties), or they don't have write access to the file (they cannot
> commit any changes to text or properties.)
>
> It sounds like you're trying to "control developers with an iron
> fist". If they change a property, wouldn't you see an email saying
> so, and wouldn't you scold the user?
>
> (Are you also planning to prevent users from breaking and stealing
> locks?)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jul 20, 2005, at 1:42 PM, Phil wrote:
> yes I want to disable all concurrency...
>
> And on that note, how can I disable users from changing file
> properties in subversion... I mean if I give a user write access can
> they change the files properties?
>
>
Yes, they can, and there's no way to stop them. Either they have
write access to the file (can commit changes to a file's text and
properties), or they don't have write access to the file (they cannot
commit any changes to text or properties.)
It sounds like you're trying to "control developers with an iron
fist". If they change a property, wouldn't you see an email saying
so, and wouldn't you scold the user?
(Are you also planning to prevent users from breaking and stealing
locks?)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
actually CVS works very well for this... Basically what I want is to
have the files checked out read only be default and require them to
lock them prior to working on them.
Now I like some of Subversion's features... Especially the browse
feature... And it seems it will work just fine. There is an entire
section in the manual on how to do this.
However is it possible to prevent users that have write access from
changing file properties...? that is where I am confused, because at
first look it appears anyone with write access can change any of the
file properties?
Or am I missing something.
On 7/20/05, Patrick Burleson <pb...@gmail.com> wrote:
> On 7/20/05, Phil <pl...@gmail.com> wrote:
> > yes I want to disable all concurrency...
> >
> > And on that note, how can I disable users from changing file
> > properties in subversion... I mean if I give a user write access can
> > they change the files properties?
>
> You know, SVN may not be the right product for you. Sounds like you
> need a central controlled designed system. This is just not how SVN is
> designed to be used. You'll be fighting it all the way.
>
> I don't know of any free systems that do the central server system,
> but you might want to look into Perforce if you need this kind of
> design.
>
> Patrick
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Patrick Burleson <pb...@gmail.com>.
On 7/20/05, Phil <pl...@gmail.com> wrote:
> yes I want to disable all concurrency...
>
> And on that note, how can I disable users from changing file
> properties in subversion... I mean if I give a user write access can
> they change the files properties?
You know, SVN may not be the right product for you. Sounds like you
need a central controlled designed system. This is just not how SVN is
designed to be used. You'll be fighting it all the way.
I don't know of any free systems that do the central server system,
but you might want to look into Perforce if you need this kind of
design.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
most of our documents are binairies so that concurrency does not
matter really...
And merging for binairies is not possible in our case.
Thanks.
On 7/20/05, David Weintraub <qa...@gmail.com> wrote:
> You sure you want to disable all concurrency? I wouldn't do that
> unless there's a requirement at your company that requires file
> locking. Locking gives you a false sense of security in concurrency
> and is a big administrative headache. (See
> <http://svnbook.red-bean.com/en/1.1/ch02s02.html#svn-ch-2-sect-2.2>).
> Almost all modern version control systems now eliminate the need for
> file locking.
>
> I have a pre-commit Perl script that will verify that properties are
> correctly set (as well as a few other rather useful things). You can
> easily set the hook to make sure that the svn:needs-lock property is
> set on all files, but not on directories. If you're interested, send
> me an email, and I'll send you the script.
>
> On 7/20/05, Phil <pl...@gmail.com> wrote:
> > yes I want to disable all concurrency...
> >
> > And on that note, how can I disable users from changing file
> > properties in subversion... I mean if I give a user write access can
> > they change the files properties?
> >
> >
> >
> >
> > On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
> > >
> > > On Jul 20, 2005, at 1:29 PM, Phil wrote:
> > >
> > > > I did and this is what I am try to issue:
> > > >
> > > > svn propset svn:needs-lock * reponame
> > > >
> > > > does nto work...?
> > > >
> > > > I need specific help... what specifically do I need to issue as a
> > > > command to set the property to all the subdirectories below my
> > > > repository that I have called 'reponame'?
> > > >
> > > > everything I tried gives me the error:
> > > > '.' is not a working copy
> > > >
> > >
> > > You can only lock files, not directories. Therefore, it only makes
> > > sense to set 'svn:lock' property on files.
> > >
> > > It sounds, then, like you want to run 'svn propset' on every file in
> > > your working copy. To do this, use your shell, or write a simple
> > > script of some sort.
> > >
> > > (Are you really certain that you want to completely disable
> > > concurrency on the whole project? You want to force people to lock
> > > *every* file before they begin editing?)
> > >
> > >
> >
>
>
> --
> --
> David Weintraub
> qazwart@gmail.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by David Weintraub <qa...@gmail.com>.
You sure you want to disable all concurrency? I wouldn't do that
unless there's a requirement at your company that requires file
locking. Locking gives you a false sense of security in concurrency
and is a big administrative headache. (See
<http://svnbook.red-bean.com/en/1.1/ch02s02.html#svn-ch-2-sect-2.2>).
Almost all modern version control systems now eliminate the need for
file locking.
I have a pre-commit Perl script that will verify that properties are
correctly set (as well as a few other rather useful things). You can
easily set the hook to make sure that the svn:needs-lock property is
set on all files, but not on directories. If you're interested, send
me an email, and I'll send you the script.
On 7/20/05, Phil <pl...@gmail.com> wrote:
> yes I want to disable all concurrency...
>
> And on that note, how can I disable users from changing file
> properties in subversion... I mean if I give a user write access can
> they change the files properties?
>
>
>
>
> On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
> >
> > On Jul 20, 2005, at 1:29 PM, Phil wrote:
> >
> > > I did and this is what I am try to issue:
> > >
> > > svn propset svn:needs-lock * reponame
> > >
> > > does nto work...?
> > >
> > > I need specific help... what specifically do I need to issue as a
> > > command to set the property to all the subdirectories below my
> > > repository that I have called 'reponame'?
> > >
> > > everything I tried gives me the error:
> > > '.' is not a working copy
> > >
> >
> > You can only lock files, not directories. Therefore, it only makes
> > sense to set 'svn:lock' property on files.
> >
> > It sounds, then, like you want to run 'svn propset' on every file in
> > your working copy. To do this, use your shell, or write a simple
> > script of some sort.
> >
> > (Are you really certain that you want to completely disable
> > concurrency on the whole project? You want to force people to lock
> > *every* file before they begin editing?)
> >
> >
>
--
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
yes I want to disable all concurrency...
And on that note, how can I disable users from changing file
properties in subversion... I mean if I give a user write access can
they change the files properties?
On 7/20/05, Ben Collins-Sussman <su...@collab.net> wrote:
>
> On Jul 20, 2005, at 1:29 PM, Phil wrote:
>
> > I did and this is what I am try to issue:
> >
> > svn propset svn:needs-lock * reponame
> >
> > does nto work...?
> >
> > I need specific help... what specifically do I need to issue as a
> > command to set the property to all the subdirectories below my
> > repository that I have called 'reponame'?
> >
> > everything I tried gives me the error:
> > '.' is not a working copy
> >
>
> You can only lock files, not directories. Therefore, it only makes
> sense to set 'svn:lock' property on files.
>
> It sounds, then, like you want to run 'svn propset' on every file in
> your working copy. To do this, use your shell, or write a simple
> script of some sort.
>
> (Are you really certain that you want to completely disable
> concurrency on the whole project? You want to force people to lock
> *every* file before they begin editing?)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jul 20, 2005, at 1:29 PM, Phil wrote:
> I did and this is what I am try to issue:
>
> svn propset svn:needs-lock * reponame
>
> does nto work...?
>
> I need specific help... what specifically do I need to issue as a
> command to set the property to all the subdirectories below my
> repository that I have called 'reponame'?
>
> everything I tried gives me the error:
> '.' is not a working copy
>
You can only lock files, not directories. Therefore, it only makes
sense to set 'svn:lock' property on files.
It sounds, then, like you want to run 'svn propset' on every file in
your working copy. To do this, use your shell, or write a simple
script of some sort.
(Are you really certain that you want to completely disable
concurrency on the whole project? You want to force people to lock
*every* file before they begin editing?)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Mark Phippard <Ma...@softlanding.com>.
Phil <pl...@gmail.com> wrote on 07/20/2005 02:29:06 PM:
> I did and this is what I am try to issue:
>
> svn propset svn:needs-lock * reponame
>
> does nto work...?
>
> I need specific help... what specifically do I need to issue as a
> command to set the property to all the subdirectories below my
> repository that I have called 'reponame'?
>
> everything I tried gives me the error:
> '.' is not a working copy
Properties can only be set on a working copy. You need to checkout
everything and then set the property on all of the files in your working
copy (use the --recursive switch) and then commit the prop changes.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
I did and this is what I am try to issue:
svn propset svn:needs-lock * reponame
does nto work...?
I need specific help... what specifically do I need to issue as a
command to set the property to all the subdirectories below my
repository that I have called 'reponame'?
everything I tried gives me the error:
'.' is not a working copy
Thanks.
On 7/20/05, Patrick Burleson <pb...@gmail.com> wrote:
> On 7/20/05, Phil <pl...@gmail.com> wrote:
> > yes I have read this many times but what it fails to show is where you
> > apply the property svn:needs-lock and how do you apply it to an entire
> > directory? Is this a conf file you change?
> >
> > I have tried to find out where and how to do this but I have not found it!
> >
> > can you help?
>
> You might want to read the chapter on properties:
>
> http://svnbook.red-bean.com/en/1.1/ch07s02.html
>
>
> Patrick
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Patrick Burleson <pb...@gmail.com>.
On 7/20/05, Phil <pl...@gmail.com> wrote:
> yes I have read this many times but what it fails to show is where you
> apply the property svn:needs-lock and how do you apply it to an entire
> directory? Is this a conf file you change?
>
> I have tried to find out where and how to do this but I have not found it!
>
> can you help?
You might want to read the chapter on properties:
http://svnbook.red-bean.com/en/1.1/ch07s02.html
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by Phil <pl...@gmail.com>.
yes I have read this many times but what it fails to show is where you
apply the property svn:needs-lock and how do you apply it to an entire
directory? Is this a conf file you change?
I have tried to find out where and how to do this but I have not found it!
can you help?
On 7/20/05, David Weintraub <qa...@gmail.com> wrote:
> Since the "published" books only deal with 1.0 and 1.1, locking won't
> be in either of those.
>
> Instead, look at the nightly build "book" at
> <http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html>.
>
> Locking is pretty simple to implement. All you have to do is set a
> property "svn:lock" on files you want to force locking, and learn the
> new "svn lock" and "svn unlock" commands. Okay, there's a bit more
> than this, but not much. It's all in the URL I provided.
>
> BTW, I installed Subversion 1.2 over 1.13 and it seemed to work
> beautifully with no problems until I tried doing stuff with locking.
> If you're using Apache, you have to replace the two Subversion modules
> in the Apache module directory.
>
> On 7/20/05, Romain Prévost <pr...@gmail.com> wrote:
> > Hi,
> >
> > I'd like to learn how to use and setup my server to be able to use
> > locks, but I can't find any documentation in the SVN book. Can someone
> > give me more information ?
> >
> > Thanks a lot.
> >
> > --
> > Romain Prévost
> > Epitech promotion 2007
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
>
>
> --
> --
> David Weintraub
> qazwart@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by steveking <st...@gmx.ch>.
David Weintraub wrote:
> Locking is pretty simple to implement. All you have to do is set a
> property "svn:lock" on files you want to force locking, and learn the
That property name would be "svn:needs-lock", not "svn:lock".
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Documentation about the 'Lock' feature
Posted by David Weintraub <qa...@gmail.com>.
Since the "published" books only deal with 1.0 and 1.1, locking won't
be in either of those.
Instead, look at the nightly build "book" at
<http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html>.
Locking is pretty simple to implement. All you have to do is set a
property "svn:lock" on files you want to force locking, and learn the
new "svn lock" and "svn unlock" commands. Okay, there's a bit more
than this, but not much. It's all in the URL I provided.
BTW, I installed Subversion 1.2 over 1.13 and it seemed to work
beautifully with no problems until I tried doing stuff with locking.
If you're using Apache, you have to replace the two Subversion modules
in the Apache module directory.
On 7/20/05, Romain Prévost <pr...@gmail.com> wrote:
> Hi,
>
> I'd like to learn how to use and setup my server to be able to use
> locks, but I can't find any documentation in the SVN book. Can someone
> give me more information ?
>
> Thanks a lot.
>
> --
> Romain Prévost
> Epitech promotion 2007
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org