Wish List for Subversion

At the risk of getting shot, I would like to put in a plug for tags as in
CVS. I have read the subversion book fairly closely and don't understand the
rationale for treating a tag like a branch. As a lightweight CVS user, I
appreciate being able to:

1. Use the rtag command to label snapshots in the development cycle with
long tags that tell what the snapshot means, e.g.,
"v16may2003_draft_to_customer."

2. Use the history command like so:

  cvs history -T | fgrep <module name>

to see tags in date order.

I also like the use of the environment variable CVSROOT to let cvs know the
location of the repository. I think that would be very useful for
subversion so one wouldn't have to enter the repository name, just the
subdirectory of interest (whether remote or local).

I'm ready to start trying subversion now that someone found the Berkeley DB
problem with Rh 9. I look forward to what I see as the most valuable
capabilities of subversion for my typical use:

  + ability to version binary files without completely duplicating the whole
file with each change

  + ability to truly version the module tree structure

  + local change history (and revert capability) to aid development while on
the road

  + ability to convert the working directory (or specific files) in place to
a previous revision

Thanks to all the subversion developers--this project has been sorely
needed!

Tom Browder
SRS Technologies, Inc.
Fort Walton Beach, Florida

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 17 18:26:42 2003