From: Yann Dirson <ydirson@altern.org>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 3/3] Some clarifications to the main doc.
Date: Sat, 10 Mar 2007 00:18:48 +0100 [thread overview]
Message-ID: <20070309231848.30705.65625.stgit@gandelf.nowhere.earth> (raw)
In-Reply-To: <20070309231444.30705.72292.stgit@gandelf.nowhere.earth>
Signed-off-by: Yann Dirson <ydirson@altern.org>
---
Documentation/stg.txt | 24 +++++++++++++++++++-----
1 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/Documentation/stg.txt b/Documentation/stg.txt
index 60a6f9c..7d92356 100644
--- a/Documentation/stg.txt
+++ b/Documentation/stg.txt
@@ -21,19 +21,33 @@ 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
-------
next prev parent reply other threads:[~2007-03-09 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 23:18 [PATCH 0/3] "stg cp", and StGIT doc updates Yann Dirson
2007-03-09 23:18 ` [PATCH 1/3] Add 'stg cp' command Yann Dirson
2007-03-09 23:18 ` [PATCH 2/3] Do not link to docs that will never be written Yann Dirson
2007-03-09 23:18 ` Yann Dirson [this message]
2007-03-12 16:20 ` [PATCH 0/3] "stg cp", and StGIT doc updates Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070309231848.30705.65625.stgit@gandelf.nowhere.earth \
--to=ydirson@altern.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).