Provided by: guilt_0.30-1_all
guilt - quilt on top of git
guilt COMMAND [ARGS]
Andrew Morton originally developed a set of scripts for maintaining
kernel patches outside of any SCM tool. Others extended these into a
suite called quilt. The basic idea behind quilt 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. This makes it difficult to visualize your
Guilt allows one to use quilt functionality on top of a Git repository.
Changes are maintained as patches which are committed into Git. 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.
In Guilt, all the patches are stored in .git/patches/$branch/, where
$branch is the name of the branch being worked on. This means that one
can have a independent series of patches for each branch present in the
repository. Each of these per-branch directories contains 2 special
series: This file contains a list of all the patch filenames relative
to the per-branch patch directory. Empty and commented out lines are
status: This file contains the state of the stack. What patches are
Any guilt operation may execute zero or more hook scripts which can be
used to run any houskeeping commands or even abort the execution of the
Guilt follows the same basic design of hooks in Git itself. All Guilt
hooks are executable files (generally shell scripts, but they can be
anything the operating system can execute) in .git/hooks/guilt/.
The following hooks are supported:
delete <patch name>
Executed when a patch is deleted from the patch series via
Autotagging is a feature that automatically creates unannotated tags
for top, bottom, and base of the stack.
On every push or pop operation (refresh is a pop followed by a push),
Top: Top-most applied patch/commit
Bottom: Bottom-most applied patch/commit
Base: Commit on top of which the bottom most patch is applied
Having these three tags, one can easily get the log/diff/other
information only for commits that are (or are not!) part of the patch
Since some users may not want to have Guilt autotag, a Git config
setting guilt.autotag can be used to turn it on or off.
If none of the config files (system, global, etc.) contain a
guilt.autotag, the feature defaults to being on.
If one or more config file contains the value, regular
git-config(1) rules apply.
During guilt-init(1), the rules are:
If none of the config files contain guilt.autotag, the repository
config file´s guilt.autotag is set to the default (on).
If there already exists a setting in any of the config files, and
neither of the autotagging related options is used, no local value
If there already exists a setting in any of the config files, but
an autotagging option is specified, the repository config file´s
guilt.autotag is set to the value specified on the command line.
All commands can be called with or without a dash. e.g. guilt add or
guilt-add - Add a file to git and guilt.
guilt-applied - List applied patches.
guilt-branch - Branch the entire patch series.
guilt-commit - Commit specified number of patches.
guilt-delete - Delete a patch.
guilt-diff - Outputs various diffs.
guilt-export - Export a patch series (to be used by quilt).
guilt-files - Print the list of files that the topmost patch
guilt-fold - Fold a specified patch into the topmost applied patch.
guilt-fork - Fork the topmost applied patch.
guilt-graph - Create a patch dependency graph.
guilt-header - Print a patch header.
guilt-help - open man page of a guilt command.
guilt-import-commit - Import one or more commits as patches.
guilt-import - Import specified patch file.
guilt-init - Initialize guilt for use in a git repository.
guilt-new - Create a new patch.
guilt-next - Output the name of next patch to be pushed.
guilt-patchbomb - Email a series of commits interactively.
guilt-pop - Pop patches from the tree.
guilt-prev - Output name of second topmost applied patch.
guilt-push - Push patches onto the tree.
guilt-rebase - Rebase pushed patches.
guilt-refresh - Refresh topmost applied patch.
guilt-repair - Repair the repository state.
guilt-rm - Remove a file from the git tree and guilt.
guilt-series - Print the stack of patches.
guilt-status - Print the status of files since the last refresh.
guilt-top - Output name of topmost applied patch.
guilt-unapplied - List all unapplied patches.
Written by Josef "Jeff" Sipek <email@example.com>
Documentation by Brandon Philips <firstname.lastname@example.org> and Josef "Jeff"
Part of the guilt7 suite (Generated for Guilt )