> > b) Give me the log entries for the changes made between
> > xyz_1-0-8 and xyz_1-0-9. Efficiently.
> Easy in Subversion, or at least not terribly hard. And
AFAIK it is multi-step operation (find where first tag was
copied, find where the second tag was copied, then log between
those revisions in the main directory). Not too easy (and not
too well handled by GUI tools)
> > e) Reconsider the efficiency of the operations above
> > considering my repository contains 347 separately tagged
> > modules, a lot of which have large history of 100 and more
> > tags
> Those numbers should have no effect on the amount of time it
> takes to do (b), (c), or (d) in Subversion, but they might
> affect (a).
Add to that the presence of gui tools. I tried RapidSvn. Having
tags directory with no more than 100 tags causes it to
recalculate something for 30 seconds every time I click tags
directorly.... Just to view what's inside...
> > e) I don't know anyone to commit to the tag once the tag is
> > placed. What could I do?
> Tell them not to. Watch commits, revert it if they do?
> You can also use one of the many authorization systems to
> protect the tags/ subdir so only a certain user can commit to
> it... It could be you, but under a special username.
The problem is that I want to restrict accidental tags changes,
Using CVS I frequently happen to multi-step place one tag (tag
some files, then tag some other files with the same tag). It is
also useful to sometimes deliberately change some file version
within the tag.
At the same time CVS will not allow me to accidentally commit
within the directory checked out by the tag.
I can't imagine how could I configure subversion so it reproduced
the behaviour above...
> > The case illustration using CVS: trunk /libs/xyz is heavily
> > reorganized, so I do
> > cvs up -r stable_tag /libs/xyz
> > as I use this library while working on something else
> > (in subversion I would svn switch)
> > Some days later I forgot about the tag checkout and do some
> > modification to the files in my xyz working copy. Then I try
> > to commit.
> > CVS refuses to commit so I know that I either should branch
> > or return to the trunk or resign.
> > Subversion allows to commit.
> Subversion would disallow the commit if you didn't have
> authorization to commit to tags/. Solve one problem, and
> you've solved the other.
But if I don't have this authorization, I will not be able to
create the tag!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Apr 2 23:16:55 2004