I noticed recently that there are some projects evolving around subversion,
some with different wc-functionalities (subversion with .svn, svk with
depots, and I believe some other)
Now I'd like to gather the known properties for files, so that not every
client uses some property names and gets incompatible with the other clients.
Please have a look at the list below and reply with properties you know, so
that a comprehensive list can be put on the subversion-website (if that's ok
with the subversion developers)
I apologize for any misunderstanding I had while compiling this list - please
feel free to correct me.
------ List follows ------
1 - Official and currently used. These won't be changed and are respected by
the clients, I believe.
Stores the x-bit for unixes
Differentiates between text and binary files, may specify other special cases
in the future (which editor to use, diff-programs, etc.)
Tells svn which files to ignore in a directory. (Does svk support this?)
Specifies dynamically translated content for text-files
To support files with specific line-ending needs
Is used to include other projects.
Logs the message in revisions.
The author for a revision
The timestamp for a committed revision.
These are currently
committed-rev, name, committed-date, url, last-author, kind, uuid,
prop-time, revision, checksum
I believe that at least the checksum (which is stored in the repository as
well) should be accessible by a
2 - Not "official" (as in listed on a central website), but in use.
Stores information regarding revision which have been merged in svk.
Was/Is used by my old patch which records a file's modification time and sets
it upon export.
Is mentioned in the viewcvs mailing list:
Stores the path to the imported sources for svm
Stores the uuid of the "other" repository (?)
----- svk:copied_from:* and svk:copied_from_keep:*
Used in svk to record the source of copied data
Used in SVN::Mirrror (http://search.cpan.org/~clkao/SVN-Mirror-0.27/)
Tells the revision (?) for svm
3 - Properties I'd like to propose, so that clients have a common
understanding of them.
Note: they point in the direction of using svn as a backing store for backup
and restore - as that's where I'll try to use subversion in the future.
----- svn:unix-owner, svn:unix-group
Both could be in the form of "name (number)". The name should be used, if not
accessible, the id.
Of course that would be useable only for uid's 0 - other could just commit
this info for files.
Records the unix-permissions (in the octal form of 0755, 02750 (group sticky
bit), and so on)
Stores the windows-acl's in a similar form to svn:unix-mode.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 17 10:38:05 2004