From ee7952008cd7fc059132b78c6c31cd8bf20a5199 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Mon, 16 Sep 2013 11:02:58 +0200 Subject: tig and bugseverywhere MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- using-git.texinfo | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/using-git.texinfo b/using-git.texinfo index d41ec77..b0ed795 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -58,6 +58,7 @@ Texts. A copy of the license is included in the section entitled * I just don't know what went wrong:: * Version control:: * Interface:: +* Beyond Git:: * GNU Free Documentation License:: * Glossary:: @end menu @@ -1295,6 +1296,46 @@ is annoying. +@node Beyond Git +@chapter Beyond Git + +@menu +* Additional tools:: +@end menu + + + +@node Additional tools +@section Additional tools + +Git is used for source control, for +a complete, possibily collaborative, +development environment you additional +tools. + +Everything git can do, you can do in +the command line, but some repetitive +gets cumbersome in the command line +because you will need to run the same +command in unpre-predictable variations. +For this the package and command +@command{tig} may be just want you need +if you live in the terminal. + +@command{bugseverywhere} is a grate tool +for keeping track of issues in git repositories. +Issues are commited to the current branch +you are working on, meaning that you can +have separate issues in separate branches. +So if you have separate branches for separate +features that are being implemented you can +create separate issues inside those branches. +And when a branch get merged with your develop +branch the unresolved issues is merged into +the develop branch. + + + @node GNU Free Documentation License @appendix GNU Free Documentation License @include fdl.texinfo -- cgit v1.2.3-70-g09d2