this post was submitted on 16 Jul 2024
23 points (100.0% liked)

Git

2874 readers
15 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
canpolat@programming.dev
jnovinger@programming.dev
23
How has Git changed the way you think about version control? (programming.dev)
submitted 3 months ago by canpolat@programming.dev to c/git@programming.dev
9 comments fedilink hide all child comments
 

Coming from CVS and ClearCase it took me some time to adopt to Git. The fact that it was distributed was confusing at first, for example, because I thought that would cause chaos. But the way we used it was actually not "that distributed". But once I understood how it worked, not doing DVCS was "the wrong way" immediately.

you are viewing a single comment's thread
view the rest of the comments
[–] BillSchofield@lemmy.world 3 points 3 months ago (1 children)

Local vcs let's you decouple saving progress (commit) from publishing your change (push).

This is a huge improvement over exclusive locks (old visual source safe) and shared server (like perforce).

There are many other improvements, but that is the one that had the most impact on my daily workflow.

[–] andioop@programming.dev 2 points 3 months ago

I had a sad incident where I had committed changes but not pushed, and then I accidentally spilled a drink on my computer and bricked it. Even though this is unlikely to happen again because I won't bring open containers like mugs or bowls of soup around computers anymore (water bottles are fine), and it was only three hours of work lost, because of this incident I do not feel I have saved until I have pushed. "What if you brick your computer again, huh, where's all that progress now?"

But overall I agree about decoupling saving changes from actually publishing them!