X-Git-Url: https://git.distorted.org.uk/~mdw/stgit/blobdiff_plain/c2b87fa2ef44a58d3ffe3dcf8cb693ad66263e9e..5fe419ab86c57856254b3d85c69fc825e33c865d:/Documentation/stg.txt?ds=sidebyside diff --git a/Documentation/stg.txt b/Documentation/stg.txt index 60a6f9c..cf28b02 100644 --- a/Documentation/stg.txt +++ b/Documentation/stg.txt @@ -1,4 +1,4 @@ -stg(7) +stg(1) ====== Yann Dirson v0.12.1, February 2007 @@ -10,7 +10,9 @@ stg - manage stacks of patches using the GIT content tracker SYNOPSIS -------- [verse] -'stg' [--version] [--help] [OPTIONS] [ARGS] +'stg' [--version | --help] +'stg' [--help | --help] +'stg' [COMMAND OPTIONS] [ARGS] DESCRIPTION ----------- @@ -21,23 +23,41 @@ GIT. These operations are performed using GIT commands and the patches are stored as GIT commit objects, allowing easy merging of the StGIT patches into other repositories using standard GIT functionality. +An StGIT stack is a GIT branch with additional information to help +making changes to individual patches you already committed, rather +than making changes by adding new commits. It is thus a +non-forwarding, or rewinding branch: the old head of the branch is +often not reachable as one of the new head's ancestors. + Typical uses of StGIT include: Tracking branch:: - Maintaining modifications against a remote branch, possibly - with the intent of sending some patches upstream. StGIT - assists in preparing and cleaning up patches until they are - acceptable upstream, as well as maintaining local patches not - meant to be sent upstream. + Tracking changes from a remote branch, while maintaining local + modifications against that branch, possibly with the intent of + sending some patches upstream. StGIT assists in preparing and + cleaning up patches until they are acceptable upstream, as + well as maintaining local patches not meant to be sent + upstream. ++ +In such a setup, typically all commits on your branch are StGIT +patches; the stack base is the branch point where your changes "fork" +off their parent branch. Development branch:: Preparing and testing your commits before publishing them, separating your features from unrelated bugfixes collected while developping. ++ +In such a setup, not all commits on your branch need to be StGIT +patches; there may be regular GIT commits below your stack base. OPTIONS ------- +The following generic option flags are available. Additional options +are available per-command, and documented in the command-specific +documentation. + --version:: Prints the StGIT suite version that the 'stg' program came from, as well as version of other components used, such as GIT @@ -117,6 +137,8 @@ stglink:goto[]:: stgdesc:goto[] stglink:float[]:: stgdesc:float[] +stglink:bury[]:: + stgdesc:bury[] stglink:applied[]:: stgdesc:applied[] stglink:unapplied[]::