[CPLUG] Dual-boot Linux

[Mark Gius]

The problem I have with git on school machines is that since you're
making all of your commits locally, if you don't for whatever reason
push to an external server and vogon goes down (a frequent occurrence),
you've just lost your work.  Since SVN doesn't allow local commits, all
of your changes are automatically synced to an external server without
any extra effort (assuming you have an external server to dump to).

So, assuming that vogon and school machines are an unreliable storage
location (a valid assumption IMO), git becomes less attractive since
there is no offsite backup, and if you do start doing offsite "pushes"
you end up with a system no better than SVN.

Git offers a lot for group projects, but I see no advantage to it for
single-user scenarios.

Mark

On Mon, 2009-01-12 at 22:56 -0800, Joshua J. Berry wrote:
> (As an aside: I don't know where people got the idea that distributed source 
> control is complicated.  It's not.  As David said, the early versions of Git 
> were atrocious, but before Git, there was BitKeeper, and Darcs, and Mercurial, 
> and ...  I found Darcs, in particular, to be even simpler than SVN.  But 
> anyway.)
> 
> On Thursday 08 January 2009 22:36:56 William Tracy wrote:
> > If you don't want to spends hours and hours just learning how to use
> > the tools, learn Subversion (svn). You'll eventually need to use
> > Subversion whenever you have a group project, anyway. (Unless you're
> > willing to teach the rest of your team to use Git, because the
> > professor won't.)
> 
> The basics take 5 minutes or less to learn, if you're already familiar with 
> CVS or SVN.
> 
> svnadmin init -> git init
> svn checkout -> git clone
> svn update -> git pull
> svn commit -> git commit -a; git push
> svn log -> git log
> svn diff -> git diff
> svn status -> git status
> 
> And of course, there are commands to add, delete and switch branches.
> 
> Or if the rest of your team *insists* on using svn, and you want to use git 
> (assuming you have a standard branches/tags/trunk setup in svn):
> 
> svn checkout -> git svn clone
> svn update -> git svn rebase
> svn commit -> git commit -a (possibly multiple times); git svn dcommit
> etc.
> 
> (Yes, git--or a part of it--knows how to speak SVN.)
> 
> -- Josh
> 
> 
> _______________________________________________
> Cplug mailing list
> Cplug at lists.cplug.org
> http://lists.cplug.org/mailman/listinfo/cplug