$ svn commit
Adding foo.py
Transmitting file data .
Committed revision 2.
If we run the info command again on our working copy and the repository we will
see that something is wrong! The repository is indeed on revision 2, but our working
copy is still on revision 1. How did that happen? The reason is that our working
copy is just a copy. commit commands work directly on the repository as we saw
earlier. Resynchronizing our working copy with the repository is easy with the
update command.
9. Type svn update and press Enter.
The next command we will see is very useful, although of course it could be argued
that they are all useful. The command in question is log, which allows us to see the
history of a repository or even a specific file or folder within it.
10. Type svn log and press Enter.
$ svn log
----------------------------------------------------------------------
r2 | user@example.com | 2007-08-12 14:26:46 +0100 (Sun, 12 Aug 2007) |
3 lines
Created sample script.
----------------------------------------------------------------------
r1 | user@example.com | 2007-08-11 14:01:20 +0100 (Sat, 11 Aug 2007) |
1 line
Initial repository structure
----------------------------------------------------------------------
Make another change to the file and check in the changes, then see how the info and
log have changed.
Pages:
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92