after reading the article at
I thought that an 'official' svn property called 'description' would
make sense. Sure, there wouldn't be any functionality depending
on that but GUI-clients could surely use such a property.
For example clients could show those descriptions in tree-views
of the filesystem right to the file entries.
Users could use that property to describe folders/files to make
it easier to identify the content of those folders/files.
I suggest that there should be a maximum length (e.g. 1024 bytes)
of that descriptions. That's because longer descriptions belong
into a separate README file and also to make it easier for clients
to implement a GUI (that way the text field showing the description
does not need to be increased in size too much).
For the subversion repository descriptions could be:
bindings interfaces for other languages than plain C
clients subversion clients
include the header files each client needs
libsvn_auth authentication files
there are several possible levels those properties could get
- only make that property 'official' and let the clients handle them
the way they want/need to.
- provide also client functions like get/setDescription for easier use
- or even include a description in the status struct
what do you guys think of that?
Received on Sat Dec 21 14:56:12 2002