On 11/15/06, Eric <email@example.com> wrote:
> At 12:46 PM 11/14/2006, Duncan Murdoch wrote:
> >> This is only a problem if you're desperately searching for problems.
> Good morning, Duncan.
> It is a problem if you're working with people who are absolutely convinced
> that it brings no benefit, and whose minds can't be changed.
> I can say "I can check out a complete set of files at rev X and I'm
> guaranteed that the spec matches the design matches the code matches the
> tests" and I hear "Yeah, yeah, you can do the same thing with VSS with
> tags" or some such.
> Never mind that it takes extra steps with VSS or CVS or most other VCSs,
> and you get it automatically with SVN.
> There are still document files, though, where it makes no sense to try to
> tie them to other files in a repository (e.g. company policies and
> procedures, correspondence, etc.) and it remains cumbersome to put each of
> them in its own repository. You can argue that it's not "bad", per se, to
> bump one revision level for largely-unrelated collections of such files,
> and that it does no harm, etc., but I will NEVER, ever, be able to convince
> the others on this team of that, even though I might, someday, be able to
> convince them to grudgingly accept the notion of a common rev number for a
> whole repository of RELATED files.
As has been mentioned before, you're not bumping the revision of any
file (the revision number is for the repository) and you're not
bumping the last changed revision for a file (this stays the same).
All you need to do is tell your users to look at the last changed
revision from 'svn info' instead of the current checkout revision.
If your users still have a problem with the revision number then I
suggest that they're irrationally opposed to SVN and you need to
either: 1) make a command decision or have someone else make one to
force people to use SVN or 2) give up for using SVN until you can get
these people fired.
(I shudder to think what your users would say about such a wonderful
system as monotone...)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 15 17:17:50 2006