[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Problem : svn: working copy locked:

From: Olivier DAVY <odavy_at_sopragroup.com>
Date: 2003-01-10 15:03:11 CET

Olivier DAVY
FRANCE (<-- see below why it is important ;))

Here is some note that I had taken during my first use of svn.
Perhaps we can enhance the guide with them.

1. the images explaining the basic concepts may not be on a green backgound
: when you copy it in its paper form with a copier, it is so black that you
can not read the text on the arrows (Well, this is a true history of a poor
user like me).

2. chapter 3 Initial checkout (p14). We may add that if the repository is
local, the URL is in the following format : file:///svn.... (And warn about
the 3 slashes (solo ;) ) or file://localhost/svn....

3. chapter 3, update your working copy : explain here that svn cat is used
for svn update -r. link to the chapter that cover the functionnality.

3bis chapter 3 Make changes to your working copy : well, I was shocked by
the fact that the semantic of the -r option for add (recursive) is not the
same as the other commands. We have to debate about that ! And the
recursive behaviour by default is what I want !

4. chapter 3, examine your changes : explain what is a "pristine" (a
working copy ?), it seems that it is the first use of this word. Do not
forget that some French can become users of svn, and that French do not
have a fluent English ;)

5. chapter 3, svn diff : We must explain a bit more what is the diff

6. chapter 3, svn revert : "svn revert can undo any schedule operations".
We may advice the user that it is not a rollback (as I tough before) : You
checkout the -r1, then if you commit the pristine (new version -r2), then
you do svn revert, you do not undo to -r1 but to -r2. Well, I think we may
explain that it is not a "revert to the checkout version).

7. chapter 3, revision numbers : "These keywords allow you to perform many
common (and helpful) operations" : We must provide examples (scenarii) of
how they can be helpfull : svn revert -r BASE, svn update -r COMMITED, svn
revert -r PREV, svn co -r HEAD : Are they good examples ?

8. chapter 3, other commands, svn cleanup : can we write down the error
messages that can lead to the use of a svn cleanup (suche as the one I

9. svn export message : changes it form "Checked out revision 3" to
"Exported out revision 3"

Well the version of the guide that I had seem not to be the latest, but I
hope those comments can help improving the guide.

already enjoying svn

-----Message d'origine-----
De: Ben Collins-Sussman [SMTP:sussman@collab.net]
Date: vendredi 10 janvier 2003 14:21
A: Olivier DAVY
Cc: 'solo turn'; Philip Martin; dev@subversion.tigris.org
Objet: Re: Problem : svn: working copy locked:

Olivier DAVY <odavy@sopragroup.com> writes:

> Perhaps the first enhancement we can do is to write a more user friendly
> guide, explaining the error that could be brought during a svn add...

What error did you get?

> Do you now how can I download the guide in another format than pdf ?

The site has three formats: pdf, ps, and on-line html.
The DocBook sourcecode is in subversion's source tree.

> If svn cleanup does not take to much time, why not doing it automatically

We just answered this question on the list yesterday. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 10 15:04:03 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.