> Well. First of all you are using a special SVN usage philosophy where all
development is done in branches as the base for your argument. This is by no
way the only way to use subversion. (For example TSVN does not use this
principle. Development is done directly in trunk.) I do not think we should
limit the usability of TSVN to one philosophy only.
Yes... but who are WE to decide what philosophy the end users are to choose?
While I have one view on it, you have another view on it. Just because you
think it should be done one way doesn’t make my way invalid.
> The point is that when you tag (or branch for that matter) you generally
desire control over WHAT you are tagging. I wager that there are far more
times that you want to tag a specific tested & verified revision than any
possible revision created during your testing procedure.
Unless you follow my method in which the trunk contains a pristine version
at all times.
> The command "svn copy" is a general purpose tool. (Both for use in WC
and on the repos.) In TSVN we have separate dialogs to help users with these
different operations. (Keyword "help".) The same operation is performed, but
still we have different dialogs. I think we can (and should) design these
dialogs to be as helpful as possible.
I wasn’t talking about "svn copy" exactly... I was talking about SVN in
general. By default pretty much everything works on the HEAD of the target
unless you specify otherwise. THAT is the convention.
This is a philosophical debate to which there is no final answer. My main
point, however, is that TSVN should follow the overall SVN convention in
which operations work on HEAD by default.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jun 21 14:36:46 2006