[OT] Re: Subversion revision controll system
[OT] Re: Subversion revision controll system
- Subject: [OT] Re: Subversion revision controll system
- From: "Alastair J.Houghton" <email@hidden>
- Date: Sat, 24 May 2003 09:25:15 +0100
On Saturday, May 24, 2003, at 07:03 am, Chris Hanson wrote:
On Friday, May 23, 2003, at 05:14 PM, Simon Fraser wrote:
Hi there,
is there anybody out there working with subversion already?
I've played with it a bit. It's nice!
Agreed. It is a nice VCS, and looks like it will turn into a *very*
nice VCS.
Unfortunately it seems to still have the same fatal flaw as CVS,
namely that it litters your directories with its own ".svn"
directories.
It should work like Perforce, where the server knows about client
workspace state, or it should at least offer the option to keep your
client workspace state in another local directory that you can > specify.
No, it shouldn't. Subversion and CVS are *scalable*, in a way that
VCSs that have the server remember the client workspace state cannot
be; this is very important for the Free Software community because the
version control systems need to be accessible to *everyone* over the
Internet.
Also, tools that have the server remember the workspace state are
usually flawed in several respects; often they make it awkward (for
example) for the same user to check-out several copies of the same code
at once, and tend to get confused if you move a working copy somewhere
else on your disk. On top of which, some of them still save stuff in
your working copy (SourceSafe, for example, creates "vssver.scc"
everywhere).
It wouldn't be a good idea to let you change the directory name either,
because it lets tools that do understand CVS or Subversion work easily
with your working copy.
Third-party tools should not have to be rewritten or modified to work
around the existence of any revision control system, much less be
special-cased for specific revision control systems.
Third-party tools shouldn't be randomly traversing your source tree :-)
If they do traverse your source tree, then they should have options to
exclude files and directories; since you know which VCS you are using
for your project, it's easy to tell other tools which files/directories
to ignore.
Regards,
Alastair.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.