annotated tag objects

Signed-off-by: Mattias Andrée <maandree@operamail.com>

1 files changed, 53 insertions, 0 deletions

diff --git a/using-git.texinfo b/using-git.texinfo
index 4092616..507cd32 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -56,6 +56,7 @@ Texts. A copy of the license is included in the section entitled
 * Collaborating::
 * Basic commands::
 * I just don't know what went wrong::
+* Version control::
 * Glossary::
 * GNU Free Documentation License::
 @end menu
@@ -1120,6 +1121,58 @@ bisection.
 
 
 
+@node Version control
+@chapter Version control
+
+@menu
+* Tagging versions::
+* Cherry picking::
+@end menu
+
+
+
+@node Tagging versions
+@section Tagging versions
+
+General, programs have different release
+version. When you release a new version,
+you tag the last commit makes it into
+that version. To do this, create an
+annotated tag object and push it to your
+origin:
+
+@example
+git tag -a 'RELEASE_VERSION'
+git push origin 'RELEASE_VERSION'
+@end example
+
+Keep in mind that you will be placed
+in an deteach HEAD, and need to checkout
+the branch you want to continue your
+work on.
+
+The created tag can be refered to as
+any commit or branch.
+
+If you want to remove a tag, you
+just tell git to delete it and push
+the deletion of its reference to
+your origin:
+
+@example
+git tag -d 'RELEASE_VERSION'
+git push :refs/tags/'RELEASE_VERSION'
+@end example
+
+
+
+@node Cherry picking
+@section Cherry picking
+
+TODO
+
+
+
 @node Glossary
 @appendix Glossary