On Thu, Dec 9, 2010 at 11:00 AM, David Kelly <[email protected]> wrote:
> On Thu, Dec 09, 2010 at 09:34:56AM -0800, Steve deRosier wrote:
>>
>> My #1 reason to use Git is the fact that the repo is in your local
>> workspace. Every other system you have to be connected to the network
>> in order to do simple things like reading the commit logs, diffing
>> versions, etc.
>
> Wrong. Neither CVS nor SVN work that way. The repository can be local or
> remote. Locally one can access the repository files directly or
Double wrong. Or more accurately, misleading.
True: you can use CVS or SVN locally. However, now you can't really
use it with multiple people, removing at least one of the arguments
for using a VCS in the first place (though I recommend using a VCS
even if you're the only one on the project, even if it just for
tracking changes).
Now, if you put the {CVS|SVN} repo on your local machine, hence now
you have local access to it (just like git. well not just like, but
close enough). You can take your laptop with you and you still view
logs, commit, etc. But your coworkers can't use it until you open it
up and server it to them.
So, you can open it up and serve to your coworkers if you like: You
have to give them access via ssh or http or some other relevant
transport, but it's easy enough to do. Now, they take their laptops
to a park to work quietly, and they do an svn log... and they're
screwed because they need network access to your repo. Or worse,
since you work on your laptop, you're on an airplane and five
developers at the office don't have access to the repo.
With SVN or CVS a "server" is required. Period. That "server" may be
on your local machine and may be accessed by direct file-system
methods, but still required. And if that "server" is not accessible,
no reading logs, diffs, or commits for you.
> indirectly through a "server" app. Once you have defined the repository
> location (and method) for a project that information sticks in the
> project. One can freely jump between projects which use different
> repositories.
Yes, true. But repo information is not stored in your local
workspace. A 'svn log' still requires a trip to the real repo. If
you've got that locally on your fs, great. If not, you're
out-of-luck.
>
> One of the biggest mistakes made in Microsoft environments is to put the
> repository on a shared filesystem with multiple users accessing via
> direct file methods. With possibly different apps simultaneously
> modifying the repository one is asking for trouble, and will get it.
>
Same problem is frequent with CVS too. Oh, and also never put the
server on an NFS mount and access it even via the server... eventually
it will corrupt.
- Steve
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
