Documentation: spell 'git cmd' without dash throughout

[thirdparty/git.git] / Documentation / git-filter-branch.txt

diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
index 544836acd530cdbdc8498ddce3475c2c8c7e7dd0..cfaba2a3057c8bf3d1e1df965a6becdae6306b2b 100644 (file)
--- a/Documentation/git-filter-branch.txt
+++ b/Documentation/git-filter-branch.txt
@@ -116,7 +116,7 @@ OPTIONS
 --commit-filter <command>::
        This is the filter for performing the commit.
        If this filter is specified, it will be called instead of the
 --commit-filter <command>::
        This is the filter for performing the commit.
        If this filter is specified, it will be called instead of the

-       'git-commit-tree' command, with arguments of the form
+       'git commit-tree' command, with arguments of the form

        "<TREE_ID> [-p <PARENT_COMMIT_ID>]..." and the log message on
        stdin.  The commit id is expected on stdout.
 +
        "<TREE_ID> [-p <PARENT_COMMIT_ID>]..." and the log message on
        stdin.  The commit id is expected on stdout.
 +


@@ -127,7 +127,7 @@ have all of them as parents.
 You can use the 'map' convenience function in this filter, and other
 convenience functions, too.  For example, calling 'skip_commit "$@"'
 will leave out the current commit (but not its changes! If you want
 You can use the 'map' convenience function in this filter, and other
 convenience functions, too.  For example, calling 'skip_commit "$@"'
 will leave out the current commit (but not its changes! If you want

-that, use 'git-rebase' instead).
+that, use 'git rebase' instead).

 +
 You can also use the `git_commit_non_empty_tree "$@"` instead of
 `git commit-tree "$@"` if you don't wish to keep commits with a single parent
 +
 You can also use the `git_commit_non_empty_tree "$@"` instead of
 `git commit-tree "$@"` if you don't wish to keep commits with a single parent


@@ -196,15 +196,15 @@ the nearest ancestor that was not excluded.
 
 -f::
 --force::
 
 -f::
 --force::

-       'git-filter-branch' refuses to start with an existing temporary
+       'git filter-branch' refuses to start with an existing temporary

        directory or when there are already refs starting with
        'refs/original/', unless forced.
 
 <rev-list options>...::
        directory or when there are already refs starting with
        'refs/original/', unless forced.
 
 <rev-list options>...::

-       Arguments for 'git-rev-list'.  All positive refs included by
+       Arguments for 'git rev-list'.  All positive refs included by

        these options are rewritten.  You may also specify options
        such as '--all', but you must use '--' to separate them from
        these options are rewritten.  You may also specify options
        such as '--all', but you must use '--' to separate them from

-       the 'git-filter-branch' options.
+       the 'git filter-branch' options.

 
 
 Examples
 
 
 Examples


@@ -221,7 +221,7 @@ However, if the file is absent from the tree of some commit,
 a simple `rm filename` will fail for that tree and commit.
 Thus you may instead want to use `rm -f filename` as the script.
 
 a simple `rm filename` will fail for that tree and commit.
 Thus you may instead want to use `rm -f filename` as the script.
 

-Using `\--index-filter` with 'git-rm' yields a significantly faster
+Using `\--index-filter` with 'git rm' yields a significantly faster

 version.  Like with using `rm filename`, `git rm --cached filename`
 will fail if the file is absent from the tree of a commit.  If you
 want to "completely forget" a file, it does not matter when it entered
 version.  Like with using `rm filename`, `git rm --cached filename`
 will fail if the file is absent from the tree of a commit.  If you
 want to "completely forget" a file, it does not matter when it entered


@@ -303,7 +303,7 @@ and all children of the merge will become merge commits with P1,P2
 as their parents instead of the merge commit.
 
 You can rewrite the commit log messages using `--msg-filter`.  For
 as their parents instead of the merge commit.
 
 You can rewrite the commit log messages using `--msg-filter`.  For

-example, 'git-svn-id' strings in a repository created by 'git-svn' can
+example, 'git svn-id' strings in a repository created by 'git svn' can

 be removed this way:
 
 -------------------------------------------------------
 be removed this way:
 
 -------------------------------------------------------


@@ -314,7 +314,7 @@ git filter-branch --msg-filter '
 
 To restrict rewriting to only part of the history, specify a revision
 range in addition to the new branch name.  The new branch name will
 
 To restrict rewriting to only part of the history, specify a revision
 range in addition to the new branch name.  The new branch name will

-point to the top-most revision that a 'git-rev-list' of this range
+point to the top-most revision that a 'git rev-list' of this range

 will print.
 
 If you need to add 'Acked-by' lines to, say, the last 10 commits (none
 will print.
 
 If you need to add 'Acked-by' lines to, say, the last 10 commits (none


@@ -330,7 +330,7 @@ git filter-branch --msg-filter '
 *NOTE* the changes introduced by the commits, and which are not reverted
 by subsequent commits, will still be in the rewritten branch. If you want
 to throw out _changes_ together with the commits, you should use the
 *NOTE* the changes introduced by the commits, and which are not reverted
 by subsequent commits, will still be in the rewritten branch. If you want
 to throw out _changes_ together with the commits, you should use the

-interactive mode of 'git-rebase'.
+interactive mode of 'git rebase'.

 
 
 Consider this history:
 
 
 Consider this history: