====== Git by example ======

===== Description of project sharing without versioning =====
Developer 1:

1. Create project.
2. Tracking project snapshots. Each snapshot is stored in a directory e.g: project_yyyymmdd.
3. Share a snapshot (working version) by posting a tar.gz on website.

Developer 2:

4. Download snapshot.
5. Work on project and create own snapshots.
6. Create patches and send back with emails.

===== Using Git =====

Developer 1:

1. Create project and a git repo (google code, github...).
<code>

</code>
2. Versioning.
  * Add new files to project
<code>
git add .
</code>
This will add current folder recursively. If one of the sub-folder contains .git, this folder will be add to repo as submodule. More about submodule <...>.
  * Commit a new version.
<code>
git commit -a -m "message"
</code>
This will commit all changes to local git manifest.
3. Share project. Push project back to central repository.
<code>
git push origin master
</code>
This will copy working branch to central repo. To get info about the alias use:
<code>
git remote -v

origin	https://thuydang.de@code.google.com/p/tdinfra/ (fetch)
origin	https://thuydang.de@code.google.com/p/tdinfra/ (push)
</code>
To see all branches:
<code>
git branch
*master
other_branch
</code>
'master' is the working branch. The push command above will push the master branch to google code.

Developer 2:
4. Download project
<code>
git clone ...
</code>
The project must be downloaded as a whole. No downloading of single sub folder possible.

5. Working with project.
Merge project with local repo:
<code>
git fetch
git merge
</code>
or
<code>
git pull 
</code>

6. Push project to central repo.

===== Working with git =====
==== Undelete ====
to see the deleted files so they can be copied later:
<code>
git ls-files -d
</code>

undelete file:
<code>
git checkout -- /path/to/file
</code>
===== references =====
  * abc
  *