Version Control with Subversion

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

Inside the Working Copy Administration Area

|

179

As you can see, the entries file is essentially a list of entries. Each <entry> tag repre-

sents one of three things: the working copy directory itself (called the this directory

entry, and noted as having an empty value for its name attribute), a file in that work-

ing copy directory (noted by having its kind attribute set to

"file"), or a subdirec-

tory in that working copy (kind here is set to

"dir"). The files and subdirectories

whose entries are stored in this file are either already under version control, or (as in

the case of the file named zeta above) are scheduled to be added to version control

when the user next commits this working copy directory’s changes. Each entry has a

unique name, and each entry has a node kind.

Developers should be aware of some special rules that Subversion uses when reading

and writing its entries files. While each entry has a revision and URL associated with

it, note that not every

<entry> tag in the sample file has explicit revision or url

attributes attached to it. Subversion allows entries to not explicitly store those two

attributes when their values are the same as (in the revision case) or trivially calcula-

ble from

*

(in the url case) the data stored in the this directory entry. Note also that