Re: [PATCH] #2219 canonicalized keyword and new UUID keyword documentation

Ben Collins-Sussman wrote:
> How about the term 'locks'? We have working-copy locks, shown by 'L'
> in the status command. BerkeleyDB has private locks that it uses for
> mutexes and things ("out of locks" errors). 'svnadmin recover' and FSFS
> both take out locks on ordinary files, to manage concurrent writes
> ("trying to get exclusive lock..."). And now we have a locking feature,
> allowing users to create locks in the filesystem.

That's a good argument, except that each and everyone one of those concepts is
almost the same thing (a way to limit resource access to a single process).
"Revision keywords" are almost nothing like the keywords concept that
svn:keywords embodies. HEAD /et al/ are aliases for certain revision numbers;
they share no common behavior with the keywords in files (a concept that
Subversion inherited from CVS, granted).

I'm not that worked up about it, except for the fact that in the index of the
book, the section "Revisions: Numbers, Keywords, and Dates, Oh My!" is given
prominent billing in the "Guided Tour," but the potentially much more useful
information about expanding keywords in files is listed somewhat obliquely in
"Advanced Topics" under "Special Properties."

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org