From 16f98874ca3e3f42ea299d3dd858f91f0122d50a Mon Sep 17 00:00:00 2001
From: Junio C Hamano
+ Do not report commits up to (and including) limit. +
+diff --git a/git-cherry.txt b/git-cherry.txt index b62c97097..e6943822c 100644 --- a/git-cherry.txt +++ b/git-cherry.txt @@ -53,6 +53,9 @@ OPTIONS
::
Working branch; defaults to HEAD.
+
- Detect copies as well as renames. + Detect copies as well as renames. See also --find-copies-harder.
- For performance reasons, by default, -C option finds copies only + For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large - projects, so use it with caution. + projects, so use it with caution. Giving more than one + -C option has the same effect.
- Detect copies as well as renames. + Detect copies as well as renames. See also --find-copies-harder.
- For performance reasons, by default, -C option finds copies only + For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large - projects, so use it with caution. + projects, so use it with caution. Giving more than one + -C option has the same effect.
- Detect copies as well as renames. + Detect copies as well as renames. See also --find-copies-harder.
- For performance reasons, by default, -C option finds copies only + For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large - projects, so use it with caution. + projects, so use it with caution. Giving more than one + -C option has the same effect.
- Detect copies as well as renames. + Detect copies as well as renames. See also --find-copies-harder.
- For performance reasons, by default, -C option finds copies only + For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large - projects, so use it with caution. + projects, so use it with caution. Giving more than one + -C option has the same effect.
- Detect copies as well as renames. + Detect copies as well as renames. See also --find-copies-harder.
- For performance reasons, by default, -C option finds copies only + For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large - projects, so use it with caution. + projects, so use it with caution. Giving more than one + -C option has the same effect.
- Initialize the submodules, i.e. clone the git repositories specified - in the .gitmodules file and checkout the submodule commits specified - in the index of the containing repository. This will make the - submodules HEAD be detached. + Initialize the submodules, i.e. register in .git/config each submodule + path and url found in .gitmodules. The key used in git/config is + submodule.$path.url. This command does not alter existing information + in .git/config.
- Update the initialized submodules, i.e. checkout the submodule commits - specified in the index of the containing repository. This will make - the submodules HEAD be detached. + Update the registered submodules, i.e. clone missing submodules and + checkout the commit specified in the index of the containing repository. + This will make the submodules HEAD be detached.
@@ -348,7 +348,7 @@ update
When cloning submodules, a .gitmodules file in the top-level directory +
When initializing submodules, a .gitmodules file in the top-level directory of the containing repository is used to find the url of each submodule. This file should be formatted in the same way as $GIR_DIR/config. The key to each submodule url is "module.$path.url".
@@ -363,7 +363,7 @@ to each submodule url is "module.$path.url".diff --git a/git-submodule.txt b/git-submodule.txt index cb0424f77..f8fb80f18 100644 --- a/git-submodule.txt +++ b/git-submodule.txt @@ -23,15 +23,15 @@ status:: repository. This command is the default command for git-submodule. init:: - Initialize the submodules, i.e. clone the git repositories specified - in the .gitmodules file and checkout the submodule commits specified - in the index of the containing repository. This will make the - submodules HEAD be detached. + Initialize the submodules, i.e. register in .git/config each submodule + path and url found in .gitmodules. The key used in git/config is + `submodule.$path.url`. This command does not alter existing information + in .git/config. update:: - Update the initialized submodules, i.e. checkout the submodule commits - specified in the index of the containing repository. This will make - the submodules HEAD be detached. + Update the registered submodules, i.e. clone missing submodules and + checkout the commit specified in the index of the containing repository. + This will make the submodules HEAD be detached. OPTIONS @@ -50,7 +50,7 @@ OPTIONS FILES ----- -When cloning submodules, a .gitmodules file in the top-level directory +When initializing submodules, a .gitmodules file in the top-level directory of the containing repository is used to find the url of each submodule. This file should be formatted in the same way as $GIR_DIR/config. The key to each submodule url is "module.$path.url". -- 2.26.2