If present on a file, the client will make the file executable in Unix-hosted working copies. See the section called “File Executability”.

If present on a file, the value indicates the file's mime-type. This allows the client to decide whether line-based contextual merging is safe to perform during updates, and can also affect how the file behaves when fetched via web browser. See the section called “File Content Type”.

If present on a directory, the value is a list of unversioned file patterns to be ignored by svn status and other subcommands. See the section called “Ignoring Unversioned Items”

If present on a file, the value tells the client how to expand particular keywords within the file. See the section called “Keyword Substitution”.

If present on a file, the value tells the client how to manipulate the file's line-endings in the working copy. See the section called “End-of-Line Character Sequences”.

If present on a directory, the value is a multi-line list of other paths and URLs the client should check out. See the section called “Externals Definitions”.

If present on a file, indicates that the file is not an ordinary file, but a symbolic link or other special object.

If present on a file, tells the client to make the file read-only in the working copy, as a reminder that the file should be locked before editing begins. See the section called “Lock Communication”.

If present, contains the authenticated username of the person who created the revision. (If not present, then the revision was committed anonymously.)

Contains the UTC time the revision was created, in ISO format. The value comes from the server machine's clock.

Contains the log message describing the revision.

If present, the revision was created via the autoversioning feature. See the section called “Autoversioning”.