[PATCH 3/3] git-bundle.txt: Clarify rev-list-args restrictions
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Aug 23, 2010, 09:02 UTC
- Message-ID
- <4a2d0ecb46d274f6143caab6982535bfb678d10e.1282553586.git.git@drmicha.warpmail.net>
- In-Reply-To
- <cover.1282553585.git.git@drmicha.warpmail.net>
Currently, one could think that 'git bundle create' groks any 'git rev-list' expression. But in fact it requires a named reference to be present. Try and make this clearer.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> --- Documentation/git-bundle.txt | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt index 3cdbc72..38e59af 100644 --- a/Documentation/git-bundle.txt +++ b/Documentation/git-bundle.txt @@ -59,7 +59,8 @@ unbundle <file>:: <git-rev-list-args>:: A list of arguments, acceptable to 'git rev-parse' and - 'git rev-list', that specifies the specific objects and references + 'git rev-list' (and containg a named ref, see SPECIFYING REFERENCES + below), that specifies the specific objects and references to transport. For example, `master{tilde}10..master` causes the current master reference to be packaged along with all objects added since its 10th ancestor commit. There is no explicit
-- 1.7.2.1.52.g7f7860