From: Marc Branchaud <mbranchaud@xiplink.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration
Date: Wed, 04 Jun 2014 11:01:53 -0400 [thread overview]
Message-ID: <538F34E1.6010704@xiplink.com> (raw)
In-Reply-To: <1401833792-2486-10-git-send-email-gitster@pobox.com>
On 14-06-03 06:16 PM, Junio C Hamano wrote:
> Since the introduction of opportunisitic updates of remote-tracking
> branches, started at around f2690487 (fetch: opportunistically
> update tracking refs, 2013-05-11) with a few updates in v1.8.4 era,
> the remote.*.fetch configuration always kicks in even when a refspec
> to specify what to fetch is given on the command line, and there is
> no way to disable or override it per-invocation.
>
> Teach the command to pay attention to the --refmap=<lhs>:<rhs>
> command-line options that can be used to override the use of
> configured remote.*.fetch as the refmap.
(Your 0/9 message merely said "The new patches at the
end clarifies how remote.*.fetch configuration variables are used in
two conceptually different ways." so I was not expecting fetch to get a new
option.)
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> ---
> Documentation/fetch-options.txt | 8 ++++++++
> Documentation/git-fetch.txt | 3 +++
> builtin/fetch.c | 35 ++++++++++++++++++++++++++++++++---
> t/t5510-fetch.sh | 37 +++++++++++++++++++++++++++++++++++++
> 4 files changed, 80 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
> index 92c68c3..d5c6289 100644
> --- a/Documentation/fetch-options.txt
> +++ b/Documentation/fetch-options.txt
> @@ -72,6 +72,14 @@ endif::git-pull[]
> setting. See linkgit:git-config[1].
>
> ifndef::git-pull[]
> +--refmap=<refspec>::
> + When fetching refs listed on the command line, use the
> + specified refspec (can be given more than once) to map the
> + refs to remote-tracking branches, instead of values of
s/values/the values/
> + `remote.*.fetch` configuration variable for the remote
s/variable/variables/
> + repository. See section on "Configured Remote-tracking
> + Branches" for details.
> +
> -t::
> --tags::
> Fetch all tags from the remote (i.e., fetch remote tags
> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
> index d09736a..96c44f9 100644
> --- a/Documentation/git-fetch.txt
> +++ b/Documentation/git-fetch.txt
> @@ -93,6 +93,9 @@ This configuration is used in two ways:
> only used to decide _where_ the refs that are fetched are stored
> by acting as a mapping.
>
> +The latter use of the configured values can be overridden by giving
For consistency with my suggestions on 8/9:
s/configured values/`remote.<repository>.fetch` values/
M.
> +the `--refmap=<refspec>` parameter(s) on the command line.
> +
>
> EXAMPLES
> --------
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> index 55f457c..dd46b61 100644
> --- a/builtin/fetch.c
> +++ b/builtin/fetch.c
> @@ -45,6 +45,8 @@ static struct transport *gsecondary;
> static const char *submodule_prefix = "";
> static const char *recurse_submodules_default;
> static int shown_url = 0;
> +static int refmap_alloc, refmap_nr;
> +static const char **refmap_array;
>
> static int option_parse_recurse_submodules(const struct option *opt,
> const char *arg, int unset)
> @@ -69,6 +71,19 @@ static int git_fetch_config(const char *k, const char *v, void *cb)
> return 0;
> }
>
> +static int parse_refmap_arg(const struct option *opt, const char *arg, int unset)
> +{
> + ALLOC_GROW(refmap_array, refmap_nr + 1, refmap_alloc);
> +
> + /*
> + * "git fetch --refmap='' origin foo"
> + * can be used to tell the command not to store anywhere
> + */
> + if (*arg)
> + refmap_array[refmap_nr++] = arg;
> + return 0;
> +}
> +
> static struct option builtin_fetch_options[] = {
> OPT__VERBOSITY(&verbosity),
> OPT_BOOL(0, "all", &all,
> @@ -107,6 +122,8 @@ static struct option builtin_fetch_options[] = {
> N_("default mode for recursion"), PARSE_OPT_HIDDEN },
> OPT_BOOL(0, "update-shallow", &update_shallow,
> N_("accept refs that update .git/shallow")),
> + { OPTION_CALLBACK, 0, "refmap", NULL, N_("refmap"),
> + N_("specify fetch refmap"), PARSE_OPT_NONEG, parse_refmap_arg },
> OPT_END()
> };
>
> @@ -278,6 +295,9 @@ static struct ref *get_ref_map(struct transport *transport,
> const struct ref *remote_refs = transport_get_remote_refs(transport);
>
> if (refspec_count) {
> + struct refspec *fetch_refspec;
> + int fetch_refspec_nr;
> +
> for (i = 0; i < refspec_count; i++) {
> get_fetch_map(remote_refs, &refspecs[i], &tail, 0);
> if (refspecs[i].dst && refspecs[i].dst[0])
> @@ -307,12 +327,21 @@ static struct ref *get_ref_map(struct transport *transport,
> * by ref_remove_duplicates() in favor of one of these
> * opportunistic entries with FETCH_HEAD_IGNORE.
> */
> - for (i = 0; i < transport->remote->fetch_refspec_nr; i++)
> - get_fetch_map(ref_map, &transport->remote->fetch[i],
> - &oref_tail, 1);
> + if (refmap_array) {
> + fetch_refspec = parse_fetch_refspec(refmap_nr, refmap_array);
> + fetch_refspec_nr = refmap_nr;
> + } else {
> + fetch_refspec = transport->remote->fetch;
> + fetch_refspec_nr = transport->remote->fetch_refspec_nr;
> + }
> +
> + for (i = 0; i < fetch_refspec_nr; i++)
> + get_fetch_map(ref_map, &fetch_refspec[i], &oref_tail, 1);
>
> if (tags == TAGS_SET)
> get_fetch_map(remote_refs, tag_refspec, &tail, 0);
> + } else if (refmap_array) {
> + die("--refmap option is only meaningful with command-line refspec(s).");
> } else {
> /* Use the defaults */
> struct remote *remote = transport->remote;
> diff --git a/t/t5510-fetch.sh b/t/t5510-fetch.sh
> index 29d59ef..d78f320 100755
> --- a/t/t5510-fetch.sh
> +++ b/t/t5510-fetch.sh
> @@ -447,6 +447,43 @@ test_expect_success 'explicit pull should update tracking' '
> )
> '
>
> +test_expect_success 'explicit --refmap is allowed only with command-line refspec' '
> + cd "$D" &&
> + (
> + cd three &&
> + test_must_fail git fetch --refmap="*:refs/remotes/none/*"
> + )
> +'
> +
> +test_expect_success 'explicit --refmap option overrides remote.*.fetch' '
> + cd "$D" &&
> + git branch -f side &&
> + (
> + cd three &&
> + git update-ref refs/remotes/origin/master base-origin-master &&
> + o=$(git rev-parse --verify refs/remotes/origin/master) &&
> + git fetch --refmap="refs/heads/*:refs/remotes/other/*" origin master &&
> + n=$(git rev-parse --verify refs/remotes/origin/master) &&
> + test "$o" = "$n" &&
> + test_must_fail git rev-parse --verify refs/remotes/origin/side &&
> + git rev-parse --verify refs/remotes/other/master
> + )
> +'
> +
> +test_expect_success 'explicitly empty --refmap option disables remote.*.fetch' '
> + cd "$D" &&
> + git branch -f side &&
> + (
> + cd three &&
> + git update-ref refs/remotes/origin/master base-origin-master &&
> + o=$(git rev-parse --verify refs/remotes/origin/master) &&
> + git fetch --refmap="" origin master &&
> + n=$(git rev-parse --verify refs/remotes/origin/master) &&
> + test "$o" = "$n" &&
> + test_must_fail git rev-parse --verify refs/remotes/origin/side
> + )
> +'
> +
> test_expect_success 'configured fetch updates tracking' '
>
> cd "$D" &&
>
next prev parent reply other threads:[~2014-06-04 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:16 [PATCH v2 0/9] Clarify two uses of remote.*.fetch Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 1/9] fetch doc: update introductory part for clarity Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 2/9] fetch doc: move FETCH_HEAD material lower and add an example Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 3/9] fetch doc: update note on '+' in front of the refspec Junio C Hamano
2014-06-18 7:56 ` Michael Haggerty
2014-06-03 22:16 ` [PATCH v2 4/9] fetch doc: remove notes on outdated "mixed layout" Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 5/9] fetch doc: on pulling multiple refspecs Junio C Hamano
2014-06-04 14:44 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 6/9] fetch doc: update refspec format description Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 7/9] fetch doc: remove "short-cut" section Junio C Hamano
2014-06-04 14:46 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 8/9] fetch doc: add a section on configured remote-tracking branches Junio C Hamano
2014-06-04 14:55 ` Marc Branchaud
2014-06-04 22:17 ` Junio C Hamano
2014-06-05 15:29 ` Marc Branchaud
2014-06-05 15:40 ` [PATCH] docs: Explain the purpose of fetch's and pull's <refspec> parameter Marc Branchaud
2014-06-05 22:12 ` Junio C Hamano
2014-06-11 14:24 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration Junio C Hamano
2014-06-04 15:01 ` Marc Branchaud [this message]
2014-06-04 22:28 ` Junio C Hamano
2014-06-05 15:45 ` Marc Branchaud
2014-06-05 18:36 ` Junio C Hamano
2014-06-18 12:21 ` Michael Haggerty
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=538F34E1.6010704@xiplink.com \
--to=mbranchaud@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.