Home/ Questions/Q 6917219
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T09:42:09+00:00

I’ve recently been looking at using Git to eventually replace the CVS repository we

  • 0

I’ve recently been looking at using Git to eventually replace the CVS repository we have at work. However after watching Linus Torvalds’ video on YouTube about Git it seems that every tutorial I find suggests using Git in the same way CVS is used except that you have a local repository which I agree is very useful for speed and distribution.

However the tutorials suggest that what you do is each clone the repository you want to develop on from a remote location and that when changes are made you commit locally building up a history to help with merge control. When you are ready to commit your changes you then push them to the remote location, but first you fetch changes to check for merge conflicts (just like CVS).

However in Linus’ video he describe the functionality of Git as a group of developers working on some code pushing and fetching from each other as needed, not using a remote location i.e. a centralized location. He also describes people pushing their changes out to verifiers who fetch and push code also. So you can see it’s possible to create scalable structure within a company also.

My question is can anybody point me in the direction of some tutorials that actually explain how to do this distributed development of code using Git so that developers push and fetch code from each other with out committing to the remote repository and if possible it would be very nice to have this tutorials Eclipsed based.

Thanks in advance,
Alexei Blue.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Take a look at alblue’s blog entry on Gerrit

    This shows a workflow different from the classic centralized server such as CVS or SVN. Superficially it looks similar as you pull the source from a central Git server, but you push your commits to the Gerrit server that can compile and test the code to make sure it works before eventually pushing the changes to the central Git server.

    Now instead of pushing the changes to Gerrit, you could have pushed the code to your pair programming buddy and he could have manually reviewed and tested the code.

    Or maybe you’re going on holiday and a colleague will finish the task you’ve started. No problem, just push your changes to their Git repo.

    Git doesn’t treat any of these other Git instances any different from each other. From Git’s perspective, none of them are special.

    • 0