Creating a Local Version Control System

Now this is a post that is going to be updated time and again.. The very post that made me abandon my previous blog to move on to a Google site..
Requirement:
Need to setup a local repository.. a version control system.. Given that I use VSS (I know, please dont make faces..!) at my work place, I am used to the 'ease'.. However it may be, it sure is simple to use...! I need the repository to be platform independent, as I dual boot into Windows 7 and Ubuntu, secondly need it to be local.. Now thats the background, next is a journal...

Which one to use?
Tried:
CVS: on Ubuntu 11.4 and on windows 7.. dint find it so impressive..
TortoiseCVS: Dont know why but the options in the context menu never appeared...! :S
Mercurial: confused about its use.. yet to be tried..
Trying out git.. many friends suggest this.. seems interesting.. simple to learn, they say.. lets see!

Git setup
Alright, what helped me understand it whole was two great articles, one form tiredblogger and another from a harvard site.
Do go through them both... (And you don't have to read this page any further! :) )

Rest is for my reference, for my own understanding..
It was simple to setup..
Download and install git from the ubuntu download center... Download and install git for windows from Google code project.. Done.. Both OS set.
In windows, left almost all settings unchanged during installation..

All I need to do is to create a bare repository to start with, its better they say.. so
in a new folder:
git init --bare
Then clone it into a new repo.. That's the working folder I guess...
so..
git clone <prev folder> <new folder name>
Done..
Then create and add new file to this new folder.. Thats the first source file..
Then, add it to repo..
git add .
Commit the repo..
git commit -a -m "a message"
Push the updates to the main repo, which would otherwise have been a remote repository, the original one from which the working was cloned.
git push origin master
Cool enough.. Lets try new things..

Working on multiple OS
The local repository cant be directly used from both the OS.. so What I am gonna have to try is to work as if I am 2 different persons contributing to a project.. haven't very well understood it all yet! lets see...!

Change only the origin url!

Alright.. Now, all I need to do is change only the path / url in the git config file for the head origin! Once done, the push was fine...! :) so...
Is there a way to avoid this manual work???
like having 2 origins? remotes I mean..
In manual it is said that the remote path can also be passed from a file in $GIT_DIR/remotes
But does that create new branches? If so, that'll clutter the repository unnecessarily...
lets see...


This post will be updated as and when I learn new things..!

No comments:

Post a Comment

We need to talk, says one microservice to another

‘But how?’ asks the other service! Ever wondered how we communicate? One would not believe how complex and multi-step process it is. It in...