Hi,
I'm another lurker who has been lured out of the shadows to offer an
opinion.
Another advantage of local access to the repository is not having to
run a server. If you want to run a repository on a machine you do not
own, having to have a sever running could be a problem. You would
have to convince the admins that it was secure and that they could
trust you to run a service like this all of the time on their
machine. I'm not sure that I understand subversion well enough to
conclude this, but I believe that setting up local access only
basically solves these issues.
Back to introductions: My name is Chris Sloan. I work at Green Hills
Software on an embedded operating system. One day (about seven months
ago) I stumbled upon the Subversion web site and was really impressed.
All of my major complaints about CVS (which I use for myself as well
as for work) were listed as things that Subversion would fix and/or do
better. I would like to contribute to the coding, but at the moment I
do not have the time to do so, so I content myself with skimming the
mailing list and eagerly waiting until Subversion is ready for use.
Keep up the good work.
Chris
On Wed, Feb 28, 2001 at 01:16:50PM -0600, Ben Collins-Sussman wrote:
> Karl Fogel <kfogel@galois.ch.collab.net> writes:
>
> > > I realize local repository access has been relegated to a lower
> > > priority, but I wonder why even create it at all. It seems to me that
> > > it makes two access paths to the repository resulting in more work and
> > > more possibility of corrupted data.
> >
> > Efficiency and debuggability. [...]
> >
> > The extra work is not very great, as the code path for local access is
> > extremely short.
>
> Also, I should add: if you're just a lone user who wants to version
> some small, private thing on your personal machine (say, your /etc
> dir), do you *really* want the overhead of installing Apache and
> mod_dav? It's like swatting a fly with a Buick.
>
> This "simple" scenario is the most common use-case for tools like RCS
> and SCCS. Newbies still use CVS to scratch this itch, though. Why?
> Because CVS handles this use-case with just as little overhead as the
> older tools. I believe, therefore, that Subversion should handle this
> use-case just as efficiently.
>
Received on Sat Oct 21 14:36:24 2006