23
How has Git changed the way you think about version control? (programming.dev)
submitted 2 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
[-] best_username_ever@sh.itjust.works 2 points 2 months ago* (last edited 2 months ago)

The staging area changed the way I work for the better. When I develop something, a file can be at the same time "not modified yet," in progress where I can carefully accept or reject the modifications, and partially done when the parts have been confirmed and added to the staging area.

Once nothing is "in progress" anymore, I know that my future commit is almost perfect and I can quickly review my stuff before committing. It’s faster and more safe than other tools.

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

Git

2634 readers
1 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