From: Eric Sunshine <sunshine@sunshineco.com>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>, Jeff King <peff@peff.net>
Subject: Re: [PATCHv3 1/3] submodule: implement `module-list` as a builtin helper
Date: Mon, 31 Aug 2015 22:22:40 -0400 [thread overview]
Message-ID: <CAPig+cSF=xM5YYh_pzGFtowpSTjkX9A-ENbmsBMX7gkB8nMU4g@mail.gmail.com> (raw)
In-Reply-To: <1441068029-19158-2-git-send-email-sbeller@google.com>
On Mon, Aug 31, 2015 at 8:40 PM, Stefan Beller <sbeller@google.com> wrote:
> Most of the submodule operations work on a set of submodules.
> Calculating and using this set is usually done via:
>
> module_list "$@" | {
> while read mode sha1 stage sm_path
> do
> # the actual operation
> done
> }
>
> Currently the function `module_list` is implemented in the
> git-submodule.sh as a shell script wrapping a perl script.
> The rewrite is in C, such that it is faster and can later be
> easily adapted when other functions are rewritten in C.
>
> git-submodule.sh, similar to the builtin commands, will navigate
> to the top-most directory of the repository and keep the
> subdirectory as a variable. As the helper is called from
> within the git-submodule.sh script, we are already navigated
> to the root level, but the path arguments are still relative
> to the subdirectory we were in when calling git-submodule.sh.
> That's why there is a `--prefix` option pointing to an alternative
> path which to anchor relative path arguments.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
> diff --git a/builtin/submodule--helper.c b/builtin/submodule--helper.c
> new file mode 100644
> index 0000000..44310f5
> --- /dev/null
> +++ b/builtin/submodule--helper.c
> +static int module_list_compute(int argc, const char **argv,
> + const char *prefix,
> + struct pathspec *pathspec)
> +{
> + int i, result = 0;
> + char *max_prefix, *ps_matched = NULL;
> + int max_prefix_len;
> + parse_pathspec(pathspec, 0,
> + PATHSPEC_PREFER_FULL |
> + PATHSPEC_STRIP_SUBMODULE_SLASH_CHEAP,
> + prefix, argv);
> +
> + /* Find common prefix for all pathspec's */
> + max_prefix = common_prefix(pathspec);
> + max_prefix_len = max_prefix ? strlen(max_prefix) : 0;
> +
> + if (pathspec->nr)
> + ps_matched = xcalloc(pathspec->nr, 1);
> +
> + if (read_cache() < 0)
> + die("index file corrupt");
die(_("..."));
> + for (i = 0; i < active_nr; i++) {
> + const struct cache_entry *ce = active_cache[i];
> +
> + if (!match_pathspec(pathspec, ce->name, ce_namelen(ce),
> + max_prefix_len, ps_matched,
> + S_ISGITLINK(ce->ce_mode) | S_ISDIR(ce->ce_mode)))
> + continue;
> +
> + if (S_ISGITLINK(ce->ce_mode)) {
> + ALLOC_GROW(ce_entries, ce_used + 1, ce_alloc);
> + ce_entries[ce_used++] = ce;
> + }
> +
> + while (i + 1 < active_nr && !strcmp(ce->name, active_cache[i + 1]->name))
> + /*
> + * Skip entries with the same name in different stages
> + * to make sure an entry is returned only once.
> + */
> + i++;
> + }
> + free(max_prefix);
> +
> + if (ps_matched && report_path_error(ps_matched, pathspec, prefix))
> + result = -1;
> +
> + free(ps_matched);
> +
> + return result;
> +}
> +
> +static int module_list(int argc, const char **argv, const char *prefix)
> +{
> + int i;
> + struct pathspec pathspec;
> + const char *alternative_path;
> +
> + struct option module_list_options[] = {
> + OPT_STRING(0, "prefix", &alternative_path,
> + N_("path"),
> + N_("alternative anchor for relative paths")),
> + OPT_END()
> + };
> +
> + const char *const git_submodule_helper_usage[] = {
> + N_("git submodule--helper module_list [--prefix=<path>] [<path>...]"),
s/module_list/module-list/
> + NULL
> + };
> +
> + argc = parse_options(argc, argv, prefix, module_list_options,
> + git_submodule_helper_usage, 0);
> +
> + if (module_list_compute(argc, argv, alternative_path
> + ? alternative_path
> + : prefix, &pathspec) < 0) {
> + printf("#unmatched\n");
> + return 1;
> + }
> +
> + for (i = 0; i < ce_used; i++) {
> + const struct cache_entry *ce = ce_entries[i];
> +
> + if (ce_stage(ce))
> + printf("%06o %s U\t", ce->ce_mode, sha1_to_hex(null_sha1));
> + else
> + printf("%06o %s %d\t", ce->ce_mode, sha1_to_hex(ce->sha1), ce_stage(ce));
> +
> + utf8_fprintf(stdout, "%s\n", ce->name);
> + }
> + return 0;
> +}
> +
> +int cmd_submodule__helper(int argc, const char **argv, const char *prefix)
> +{
> + if (argc < 2)
> + die(N_("fatal: submodule--helper subcommand must be called with "
> + "a subcommand, which is module-list\n"));
> +
> + if (!strcmp(argv[1], "module-list"))
Can we drop the "module-" prefix altogether from these subcommands,
please? Considering that the parent name is already
"submodule--helper", the "module-" prefix is probably pure redundancy.
Instead:
submodule--helper list
submodule--helper name
submodule--helper clone
> + return module_list(argc - 1, argv + 1, prefix);
> +
> + die(N_("fatal: '%s' is not a valid submodule--helper subcommand, "
> + "which is module-list\n"),
> + argv[1]);
> +}
next prev parent reply other threads:[~2015-09-01 2:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 19:19 [PATCHv2 0/3] submodule--helper: Have some refactoring only patches first Stefan Beller
2015-08-31 19:19 ` [PATCH 1/3] submodule: implement `module_list` as a builtin helper Stefan Beller
2015-08-31 21:55 ` Eric Sunshine
2015-08-31 19:19 ` [PATCH 2/3] submodule: implement `module_name` " Stefan Beller
2015-08-31 20:35 ` Junio C Hamano
2015-08-31 20:51 ` Stefan Beller
2015-08-31 22:01 ` Eric Sunshine
2015-08-31 19:19 ` [PATCH 3/3] submodule: implement `module_clone` " Stefan Beller
2015-08-31 22:35 ` Eric Sunshine
2015-09-01 17:49 ` Stefan Beller
2015-09-01 18:35 ` Eric Sunshine
2015-08-31 20:15 ` [PATCHv2 0/3] submodule--helper: Have some refactoring only patches first Junio C Hamano
2015-09-01 0:40 ` [PATCHv3 " Stefan Beller
2015-09-01 0:40 ` [PATCHv3 1/3] submodule: implement `module-list` as a builtin helper Stefan Beller
2015-09-01 2:22 ` Eric Sunshine [this message]
2015-09-01 0:40 ` [PATCHv3 2/3] submodule: implement `module-name` " Stefan Beller
2015-09-01 2:31 ` Eric Sunshine
2015-09-01 16:18 ` Stefan Beller
2015-09-01 0:40 ` [PATCHv3 3/3] submodule: implement `module-clone` " Stefan Beller
2015-09-01 2:41 ` Eric Sunshine
2015-09-01 2:09 ` [PATCHv3 0/3] submodule--helper: Have some refactoring only patches first Eric Sunshine
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='CAPig+cSF=xM5YYh_pzGFtowpSTjkX9A-ENbmsBMX7gkB8nMU4g@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmail.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).