[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: feature request: svn revision alias

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Tue, 19 Feb 2008 11:07:20 -0600

> -----Original Message-----
> From: Miller, Eric [mailto:Eric.Miller_at_amd.com]
> Sent: Tuesday, February 19, 2008 10:29 AM
> To: Karl Fogel; OS
> Cc: users_at_subversion.tigris.org
> Subject: RE: feature request: svn revision alias
>
>
> Of course copies-as-tags fails in the "what tags apply to this file?"
> scenario.
 
 
Bzzzt! Not applicable due to paradigm shift and/or bad assumptions from
using RCS based systems for so long. =)

"what tags apply to this file?" is the same as asking what baselines
(aka tags) is the file in. In SVN you can search the baselines (tag
directories) for the file, or you use merging to make sure the file gets
into the various baselines/tags in the first place.

Granted, searching over a whole bunch of SVN tag directories isn't as
efficient as looking at the tags on an individual file. However, the
whole reason we've been able to do that in other RCS like systems, is
because RCS stored all information about a file on a per file basis,
which made it grossly inefficient to manipulate groups of files or to
think about all the files as a whole.

In other words, SVN encourages you to think in terms of change-sets and
baselines. RCS-based systems encourage you to think in terms of
individual files. SVN == forest. ClearCase/RCS/CVS == trees.

IMHO, thinking in terms of change-sets and baselines is better from a
process/change management/software life cycle point of view.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-19 18:07:59 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.