Git

2868 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

Follow programming.dev rules
Be excellent to each other, no hostility towards users for any reason
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

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

[–] Kissaki@programming.dev 3 points 3 months ago

How did it change how I think about version control? Not much? The goals are still the same. It only does many things better than previous centralized tools.

When DVCS came up and became popular, I used Git and Bzr.

At work, we used subversion. In one project, we had one SVN repository in our office and the customer had one in their office. A colleage had created a sync util. We regularly synced all history into an external hard drive, drove to the customer, and merged it there. Required a thorough and checklist process, potentially conflict resolution, and changelog generating for the big merge commit. Then drive back to the office, and merge back there.

Of course sometimes you used remote desktop to hotfix changes in their code base. Meaning you'd now have the change in two places as different commits.

Anyway, I've never found Git difficult. I used it, learned and understood it, and it's consistent. I know enough "internals"/technical details to understand and use it well and without confusion.