By Joey Hess, Wikis are not just for encyclopedias and Web sites anymore. You can use Ikiwiki in combination with your revision control system to handle issue tracking, news feeds, and other needs of a software project. The wiki can make your bug reports as much a part of your software project as its code, with interesting results. Ikiwiki is a wiki engine with a twist. It's best described by the term "wiki compiler". Just as a typical software project consists of source code that is stored in revision control and compiled with make and gcc, an ikiwiki-based wiki is stored as human editable source in a revision control system, and built into HTML using ikiwiki. Ikiwiki uses your revision control system to track changes and handle tasks such as rolling back changes and merging edits.
Installation of package Work with git.el Customization The git-emacs package Installation and customisation Work with existing repository Creation of new repositories Work with changes History of changes Work with tags & branches The magit package Installation and customisation Basics of work with package Work with changes Work with history of changes Tags, branches, and remote repositories The egg package Auxiliary packages git-blame gitsum egit We can work with Git using several packages — either use modules for VC и DVC packages, or use packages git.el, emacs-git, magit & egg packages. In first case we work with Git through standard interfaces of VC & DVC.
Ikiwiki is a wiki compiler. It converts wiki pages into HTML pages suitable for publishing on a website. Ikiwiki stores pages and history in a revision control system such as Subversion or Git. There are many other features, including support for blogging, as well as a large array of plugins.
Andrew Morton originally developed a set of scripts for maintaining kernel patches outside of any SCM tool - quilt whose basic idea is to maintain patches instead of maintaining source files. Patches can be added, removed or reordered, and they can be refreshed as you fix bugs or update to a new base revision. quilt is very powerful, but it is not integrated with the underlying SCM tools. The patch queue extension Mq integrates quilt functionality into Mercurial. Changes are maintained as patches which are committed into Mercurial. Commits can be removed or reordered, and the underlying patch can be refreshed based on changes made in the working directory. The patch directory can also be placed under revision control, so you can have a separate history of changes made to your patches.