cvs checkout module from tusker public repo:
git clone http://git.gplhost.com/users/tusker/dtc.git
or the master one:
git clone http://git.gplhost.com/dtc.git
cvs export:
git archive
For the cvs add/remove, there is git add/rm, but unlike CVS, each time you edit a file whose new changes you intend to commit along in the next commit, you need to re-git-add that file. Please read the git manual and git for CVS users guide for more details.
Both are available by googling for *git manual* and *git for cvs users*.
creating a list of patches:
I'm not exactly sure why we would need to share patches when we all could be pulling from each other's repositories, but:
Various ways to check your working tree
git diff (1)
git diff --cached (2)
git diff HEAD (3)
1. changes in the working tree since your last git-update-index.
2. changes between the index and your last commit; what you would be committing if you run "git commit" without "-a" option.
3. changes in the working tree since your last commit; what you would be committing if you run "git commit -a"
Pulling from somebody's git:
git pull git://example.com/project.git master # fetch and merge in remote branch
Sending a list of modifications to the master git:
In theory, the public repository COULD not be changed by several people at the same time, but I've arranged (for the time being) to be the repo master -- the one that publishes to the public repo.
Here's a list of debian packages you might want to apt-get install:
git-core
git-doc
gitk
