Everyday GIT With 20 Commands Or So
-GIT suite has over 100 commands, and the manual page for each of
-them discusses what the command does and how it is used in
-detail, but until you know what command should be used in order
-to achieve what you want to do, you cannot tell which manual
-page to look at, and if you know that already you do not need
-Does that mean you need to know all of them before you can use
-git? Not at all. Depending on the role you play, the set of
-commands you need to know is slightly different, but in any case
-what you need to learn is far smaller than the full set of
-commands to carry out your day-to-day work. This document is to
-serve as a cheat-sheet and a set of pointers for people playing
-<<Basic Repository>> commands are needed by people who has a
+<<Basic Repository>> commands are needed by people who have a
repository --- that is everybody, because every working tree of
If you work with other people, you will need commands listed in
-<<Individual Developer (Participant)>> section as well.
+<<Individual Developer (Participant)>> section as well.
-People who play <<Integrator>> role need to learn some more
+People who play <<Integrator>> role need to learn some more
commands in addition to the above.
<<Repository Administration>> commands are for system
-administrators who are responsible to care and feed git
-repositories to support developers.
+administrators who are responsible for the care and feeding
Basic Repository[[Basic Repository]]
-Everybody uses these commands to
feed and care git repositories.
+Everybody uses these commands to git repositories.
* gitlink:git-init-db or gitlink:git-clone to create a
- * gitlink:git-fsck-objects to
validate the repository.
+ * gitlink:git-fsck-objects to the repository.
- * gitlink:git-prune to garbage collect cruft in the
+ * gitlink:git-prune to remove unused objects in the repository.
* gitlink:git-repack to pack loose objects for efficiency.
-<1> pack all the objects reachable from the refs into one pack
-and remove unneeded other packs
+<1> pack all the objects reachable from the refs into one pack,
+then remove the other packs.
Individual Developer (Standalone)[[Individual Developer (Standalone)]]
* gitlink:git-log to see what happened.
- * gitlink:git-whatchanged to find out where things have
* gitlink:git-checkout and gitlink:git-branch to switch
Extract a tarball a nd create a working tree and a new repository to keep track of it.::
+ a tarball a:
$ edit/compile/test; git commit -a -s <1>
$ git format-patch origin <2>
whatchanged -p ORIG_HEAD.. arch/i386 include/asm-i386 <4>
+$ git -p ORIG_HEAD.. arch/i386 include/asm-i386 <4>
$ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL <5>
$ git reset --hard ORIG_HEAD <6>