6 guilt - quilt on top of git
10 'guilt' COMMAND [ARGS]
15 Andrew Morton originally developed a set of scripts for maintaining kernel
16 patches outside of any SCM tool. Others extended these into a suite called
17 quilt. The basic idea behind quilt is to maintain patches instead of
18 maintaining source files. Patches can be added, removed or reordered, and
19 they can be refreshed as you fix bugs or update to a new base revision.
20 quilt is very powerful, but it is not integrated with the underlying SCM
21 tools. This makes it difficult to visualize your changes.
23 Guilt allows one to use quilt functionality on top of a Git repository.
24 Changes are maintained as patches which are committed into Git. Commits can
25 be removed or reordered, and the underlying patch can be refreshed based on
26 changes made in the working directory. The patch directory can also be
27 placed under revision control, so you can have a separate history of changes
33 In Guilt, all the patches are stored in .git/patches/$branch/, where $branch
34 is the name of the branch being worked on. This means that one can have a
35 independent series of patches for each branch present in the repository.
36 Each of these per-branch directories contains 3 special files:
38 guards: This file contains any guards that should be applied to the
39 series when pushing. It is only present when guards are selected.
41 series: This file contains a list of all the patch filenames relative to the
42 per-branch patch directory. Empty and commented out lines are ignored.
44 status: This file contains the state of the stack. What patches are applied.
48 Any guilt operation may execute zero or more hook scripts which can be used
49 to run any housekeeping commands or even abort the execution of the command.
55 All commands can be called with or without a dash. e.g. 'guilt add' or
62 Written by Josef "Jeff" Sipek <jeffpc@josefsipek.net>
66 Documentation by Brandon Philips <brandon@ifup.org> and Josef "Jeff" Sipek
67 <jeffpc@josefsipek.net>