A few --shallow-exclude fixes
cover A few --shallow-exclude fixes
Here's a couple patches to fix up an error message and the documentation around the --shallow-exclude option.
Elijah Newren (2):
upload-pack: fix ambiguous error message
doc: correct misleading descriptions for --shallow-exclude
Documentation/fetch-options.txt | 2 +- Documentation/git-clone.txt | 2 +- Documentation/git-fetch-pack.txt | 2 +- builtin/clone.c | 2 +- builtin/fetch.c | 4 ++-- builtin/pull.c | 4 ++-- t/t5500-fetch-pack.sh | 7 +++++++ upload-pack.c | 6 +++++- 8 files changed, 20 insertions(+), 9 deletions(-)
base-commit: 8f8d6eee531b3fa1a8ef14f169b0cb5035f7a772
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1822%2Fnewren%2Fshallow-exclude-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1822/newren/shallow-exclude-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1822
Signature · 1 line
gitgitgadget
PATCH 1/2 upload-pack: fix ambiguous error message
From: Elijah Newren <[email protected]>
upload-pack.c takes any --shallow-exclude argument(s) from clone/fetch/etc. and passes them through expand_ref(). If it does not get back exactly one ref from the call to expand_ref(), it will die with the following error:
fatal: git upload-pack: ambiguous deepen-not: %s
Given that the documentation suggests to users that --shallow-exclude accepts a revision rather than a ref (which will be corrected in a subsequent commit), users may try to pass a revision. In such a case, expand_ref() will return 0 matches, but the error message we print will be misleading since "ambiguous" suggests there are multiple matches. Provide a clearer error message for such a case.
--- t/t5500-fetch-pack.sh | 7 +++++++ upload-pack.c | 6 +++++- 2 files changed, 12 insertions(+), 1 deletion(-)
t/t5500-fetch-pack.sh +7 -0
@@ -926,6 +926,13 @@ test_expect_success 'fetch exclude tag one' ' test_cmp expected actual ' +test_expect_success 'fetch exclude tag one as revision' ' + test_when_finished rm -f rev err && + git -C shallow-exclude rev-parse one >rev && + test_must_fail git -C shallow12 fetch --shallow-exclude $(cat rev) origin 2>err && + grep "deepen-not is not a ref:" err +' + test_expect_success 'fetching deepen' ' test_create_repo shallow-deepen && (
upload-pack.c +5 -1
@@ -1025,10 +1025,14 @@ static int process_deepen_not(const char *line, struct oidset *deepen_not, int * {const char *arg;if (skip_prefix (line,"deepen-not " , &arg)) { +int cnt;char *ref =NULL ;struct object_id oid; -if (expand_ref (the_repository, arg,strlen (arg), &oid, &ref) !=1 ) + cnt =expand_ref (the_repository, arg,strlen (arg), &oid, &ref); +if (cnt >1 )die ("git upload-pack: ambiguous deepen-not: %s" , line); +if (cnt <1 ) +die ("git upload-pack: deepen-not is not a ref: %s" , line);oidset_insert (deepen_not, &oid);free (ref); *deepen_rev_list =1 ;
Signature · 1 line
gitgitgadget
PATCH 2/2 doc: correct misleading descriptions for --shallow-exclude
In reply to Elijah Newren via GitGitGadgetFrom: Elijah Newren <[email protected]>
The documentation for the --shallow-exclude option to clone/fetch/etc. claims that the option takes a revision, but it does not. As per upload-pack.c's process_deepen_not(), it passes the option to expand_ref() and dies if it does not find exactly one ref matching the name passed. Further, this has always been the case ever since these options were introduced by the commits merged in a460ea4a3cb1 (Merge branch 'nd/shallow-deepen', 2016-10-10). Fix the documentation to match the implementation.
--- Documentation/fetch-options.txt | 2 +- Documentation/git-clone.txt | 2 +- Documentation/git-fetch-pack.txt | 2 +- builtin/clone.c | 2 +- builtin/fetch.c | 4 ++-- builtin/pull.c | 4 ++-- 6 files changed, 8 insertions(+), 8 deletions(-)
Documentation/fetch-options.txt +1 -1
@@ -29,7 +29,7 @@ Deepen or shorten the history of a shallow repository to include all reachable commits after <date>. ---shallow-exclude=<revision>:: +--shallow-exclude=<ref>:: Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. This option can be specified multiple times.
Documentation/git-clone.txt +1 -1
@@ -255,7 +255,7 @@ corresponding `--mirror` and `--no-tags` options instead. `--shallow-since=<date>`:: Create a shallow clone with a history after the specified time. -`--shallow-exclude=<revision>`:: +`--shallow-exclude=<ref>`:: Create a shallow clone with a history, excluding commits reachable from a specified remote branch or tag. This option can be specified multiple times.
Documentation/git-fetch-pack.txt +1 -1
@@ -91,7 +91,7 @@ be in a separate packet, and the list must end with a flush packet. Deepen or shorten the history of a shallow repository to include all reachable commits after <date>. ---shallow-exclude=<revision>:: +--shallow-exclude=<ref>:: Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. This option can be specified multiple times.
builtin/clone.c +1 -1
@@ -147,7 +147,7 @@ static struct option builtin_clone_options[] = { N_("create a shallow clone of that depth")),OPT_STRING (0 ,"shallow-since" , &option_since,N_ ("time" ),N_ ("create a shallow clone since a specific time" )), -OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("revision" ), +OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("ref" ),N_ ("deepen history of shallow clone, excluding rev" )),OPT_BOOL (0 ,"single-branch" , &option_single_branch, N_("clone only one branch, HEAD or --branch")),
builtin/fetch.c +2 -2
@@ -2216,8 +2216,8 @@ int cmd_fetch(int argc, N_("deepen history of shallow clone")),OPT_STRING (0 ,"shallow-since" , &deepen_since,N_ ("time" ),N_ ("deepen history of shallow repository based on time" )), -OPT_STRING_LIST (0 ,"shallow-exclude" , &deepen_not,N_ ("revision" ), -N_ ("deepen history of shallow clone, excluding rev" )), +OPT_STRING_LIST (0 ,"shallow-exclude" , &deepen_not,N_ ("ref" ), +N_ ("deepen history of shallow clone, excluding ref" )),OPT_INTEGER (0 ,"deepen" , &deepen_relative,N_ ("deepen history of shallow clone" )), OPT_SET_INT_F(0, "unshallow", &unshallow,
builtin/pull.c +2 -2
@@ -218,8 +218,8 @@ static struct option pull_options[] = {OPT_PASSTHRU_ARGV (0 ,"shallow-since" , &opt_fetch,N_ ("time" ),N_ ("deepen history of shallow repository based on time" ),0 ), -OPT_PASSTHRU_ARGV (0 ,"shallow-exclude" , &opt_fetch,N_ ("revision" ), -N_ ("deepen history of shallow clone, excluding rev" ), +OPT_PASSTHRU_ARGV (0 ,"shallow-exclude" , &opt_fetch,N_ ("ref" ), +N_ ("deepen history of shallow clone, excluding ref" ),0 ), OPT_PASSTHRU_ARGV(0, "deepen", &opt_fetch, N_("n"), N_("deepen history of shallow clone"),
Signature · 1 line
gitgitgadget
Quoted 6 lines · Elijah Newren via GitGitGadget
Here's a couple patches to fix up an error message and the documentation around the --shallow-exclude option.
Elijah Newren (2):
upload-pack: fix ambiguous error message
doc: correct misleading descriptions for --shallow-exclude
Both patches look sensible.
Will queue. Thanks.
Re: [PATCH 1/2] upload-pack: fix ambiguous error message
In reply to Elijah Newren via GitGitGadgetQuoted 7 lines · Elijah Newren via GitGitGadget
upload-pack.c +0
-0@@ -1025,10 +1025,14 @@ static int process_deepen_not(const char *line, struct oidset *deepen_not, int * {const char *arg;
upload-pack.c static int process_deepen_not(const char *line, struct oidset *deepen_not, int * · line 1035
Quoted 10 lines
upload-pack.c +5
-1if (skip_prefix (line,"deepen-not " , &arg)) { +int cnt;char *ref =NULL ;struct object_id oid; -if (expand_ref (the_repository, arg,strlen (arg), &oid, &ref) !=1 ) + cnt =expand_ref (the_repository, arg,strlen (arg), &oid, &ref); +if (cnt >1 )die ("git upload-pack: ambiguous deepen-not: %s" , line); +if (cnt <1 ) +die ("git upload-pack: deepen-not is not a ref: %s" , line);
I was wondering whether expand_ref() could ever return negative, but after reading through its implementation that doesn't seem to be the case. It's somewhat misleading that it returns int, as size_t would convey the return value in a better spirit.
Anyway, that is not an issue of this patch series, and the change looks good.
Patrick
Re: [PATCH 2/2] doc: correct misleading descriptions for --shallow-exclude
In reply to Elijah Newren via GitGitGadgetbuiltin/clone.c static struct option builtin_clone_options[] = { · line 151
Quoted 11 lines · Elijah Newren via GitGitGadget
builtin/clone.c +1
-1@@ -147,7 +147,7 @@ static struct option builtin_clone_options[] = { N_("create a shallow clone of that depth")),OPT_STRING (0 ,"shallow-since" , &option_since,N_ ("time" ),N_ ("create a shallow clone since a specific time" )), -OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("revision" ), +OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("ref" ), N_("deepen history of shallow clone, excluding rev")),
We also need to replace "rev" with "ref" here. We already do that in the other cases.
Patrick
Re: [PATCH 2/2] doc: correct misleading descriptions for --shallow-exclude
Quoted 15 lines · Patrick Steinhardt
builtin/clone.c static struct option builtin_clone_options[] = { · line 151
Quoted 11 lines · Elijah Newren via GitGitGadget
builtin/clone.c +1
-1@@ -147,7 +147,7 @@ static struct option builtin_clone_options[] = { N_("create a shallow clone of that depth")),OPT_STRING (0 ,"shallow-since" , &option_since,N_ ("time" ),N_ ("create a shallow clone since a specific time" )), -OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("revision" ), +OPT_STRING_LIST (0 ,"shallow-exclude" , &option_not,N_ ("ref" ), N_("deepen history of shallow clone, excluding rev")),We also need to replace "rev" with "ref" here. We already do that in the other cases.
Ah, I missed that one. Let me locally amend, as there does not seem to be any other issues.