<div>Thanks for the book. I have one small criticism, though:<br><br>A paragraph from the section on locking: <br></div><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Many version control systems use a
<i class="firstterm">lock-modify-unlock</i> model to address
this problem. In such a system, the repository allows only
one person to change a file at a time. First Harry must
"<span class="quote">lock</span>" the file before he can begin making
changes to it. Locking a file is a lot like borrowing a book
from the library; if Harry has locked a file, then Sally
cannot make any changes to it. If she tries to lock the file,
the repository will deny the request. All she can do is read
the file, and wait for Harry to finish his changes and release
his lock. After Harry unlocks the file, his turn is over, and
now Sally can take her turn by locking and editing. <a href="http://svnbook.red-bean.com/nightly/en/svn.basic.vsn-models.html#svn.basic.vsn-models.lock-unlock.dia-1" title="Figure 2.3. The lock-modify-unlock solution">
Figure 2.3, "The lock-modify-unlock solution"</a> demonstrates this simple
solution.<br></blockquote><br>I think the analogy of locking to a borrowing from a brick-and-mortar library is either ill-conceived or poorly explained.<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Locking a file is a lot like borrowing a book
from the library; if Harry has locked a file, then Sally
cannot make any changes to it.</blockquote><div><br>Making edits to borrowed books is highly discouraged. ;-) But besides that, I am having trouble making any useful connection between libraries and a repository that would help explain locking.
<br><br>IMO, if the "library" part were dropped, I think it would be a better paragraph.<br><br>Thanks,<br>Jamie<br></div><br><br>