*1) Update Status Descriptions
6 possible status can occur after you do a "update", per file:
U
unchanged
If C happens 3 copies of the file will be created:
A
added
and file.c.rNEW.
will have conflict markers added. You
file.c.mine,
file.c.rOLD
file.c
D
deleted
will only be able to commit again when those 3 files have been removed. This can be
R
replaced
done automatically by running svn
file.c, which removes those 3 files.
resolved
G
merged
C
conflict!
*2) Extended Status Descriptions
# svn left a lock in the .svn area of some_dir
L
some_dir
bar.c
# the content in bar.c has local modifications
M
baz.c
# baz.c has property but no content modifications
M
# dir is part of an externals definition
X
3rd_party
foo.o
# svn doesn't manage foo.o
?
# svn manages this, but it's missing or incomplete
!
some_dir
# do a
to remove it from the repo
svn delete
qux
# versioned as file/dir/link, but type has changed
~
# svn doesn't manage this, and is set to ignore it
I
.screenrc
# added with history of where it came from
A +
moved_dir
moved_dir/README
# added with history and has local modifications
M +
# file is scheduled for deletion
D
stuff/fish.c
stuff/loot/bloo.h
# file is scheduled for addition
A
stuff/loot/lump.c
# file has textual conflicts from an update
C
stuff/loot/glub.c
# file has property conflicts from an update
C
xyz.c
# file is scheduled for replacement
R
# file or dir has been switched to a branch
S
stuff/squawk
# file is locked locally; lock-token present
K dog.jpg
# file is locked in the repository by other user
O cat.jpg
# file is locked locally, but lock has been broken
B bird.jpg
# file is locked locally, but lock has been stolen
T fish.jpg
See:
*3) Import Procedure
1. Create a repo (svnadmin create)
2. Import your project (svn import)
3. Do your first checkout (svn checkout)
4. Work on checked out working copy