Ohad Lutzky wrote:
As long as you're not doing rebases or working with multiple branches
(which are much more complicated to do in SVN, and useless in the
situation at any rate), the "data loss" problems mentioned above don't
exist.
Not true. The problem can happen if you just check out a commit which is
not at the head of a branch (say, because you were doing regression
testing), and then perform a commit. No branching required.
Git gives the added bonus of being able to work offline, which
is indispensable for a student on a laptop.
True, but it steps up the complexity considerably. Well, you step it up
to begin with when you say that publishing your work requires two stages
(three if you count the "add") - commit and then push. This means that
for several people working on one repository, you would usually try to
simplify things by telling them to git add + commit + push. Then, when
you try take the laptop away, you find that you split an operation that
used to be atomic, and the complexity comes back.
True, working with a centralized repository means that this is downright
impossible, but I still maintain that working offline is no novice task.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
_______________________________________________
Haifux mailing list
Haifux@haifux.org
http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
