Consider you have a submodule at path "sub". What should happen in case
you run a command such as "git -C sub add ." ?
Here is what currently happens:
1) The submodule is populated, i.e. there is a .git (file/dir) inside
"sub". This is equivalent of running "git add ." in the submodule and
it behaves as you would expect, adding all files to the index.
2) The submodule is not populated or even not initialized.
For quite some time we got
$ git -C sub add .
git: pathspec.c:317: prefix_pathspec: Assertion `item->nowildcard_len <= item->len && item->prefix <= item->len' failed.
Aborted (core dumped)
(This is fixed by another patch in flight to not assert,
but rather die with a better message instead; but that patch is
merely a fix of a corner case in the pathspec code.)
While 1) is rather uncontroversial, there are multiple things the user
may have intended with this command in 2):
* add the submodule to the superproject
* add all files inside the sub/ directory to the submodule or
superproject.
It is unclear what the user intended, so rather error out instead.
Now let's ask the same question for "git -C sub status ." (which is a
command that is only reading and not writing to the repository)
1) If the submodule is populated, the user clearly intended to know
more about the submodules status
2) It is unclear if the user wanted to learn about the submodules state
(So ideally: "The submodule 'sub' is not initialized. To init ...")
or the status check should be applied to the superproject instead.
Avoid the confusion in 2) as well and just error out for now. Later on
we may want to add another flag to git.c to allow commands to be run
inside unpopulated submodules and each command reacts appropriately.
Signed-off-by: Stefan Beller <sbeller@xxxxxxxxxx>
---
This is the next logical step after sb/pathspec-errors (pathspec:
give better message for submodule related pathspec error). If you are in
a path that is clearly a submodules, I would expect that most users would
expect the git operation to apply to the submodule. In case of unpopulated
submodules, this is not the case though, but we apply the operation to the
superproject, which may be wrong or confusing. Hence just error out for now.
Later we may want to add a flag that allows specific commands to run in such
a setup (e.g. git status could give a fancier message than a die(..)).
I marked this as RFC
* to request for comments if this is a good idea from a UI-perspective
* because I did not adapt any test for this patch. (A lot of submodule tests
seem to break with this; From a cursory read of those tests, I'd rather
blame the tests for being sloppy than this patch damaging user expectations)
Thanks,
Stefan
git.c | 3 +++
submodule.c | 36 ++++++++++++++++++++++++++++++++++++
submodule.h | 1 +
3 files changed, 40 insertions(+)
diff --git a/git.c b/git.c
index bbaa949e9c..ca53b61474 100644
--- a/git.c
+++ b/git.c
@@ -2,6 +2,7 @@
#include "exec_cmd.h"
#include "help.h"
#include "run-command.h"
+#include "submodule.h"
const char git_usage_string[] =
"git [--version] [--help] [-C <path>] [-c name=value]\n"
@@ -364,6 +365,8 @@ static int run_builtin(struct cmd_struct *p, int argc, const char **argv)
if (prefix)
die("can't use --super-prefix from a subdirectory");
}
+ if (prefix)
+ check_prefix_inside_submodule(prefix);
if (!help && p->option & NEED_WORK_TREE)
setup_work_tree();
diff --git a/submodule.c b/submodule.c
index 73521cdbb2..357a22b804 100644
--- a/submodule.c
+++ b/submodule.c
@@ -495,6 +495,42 @@ void set_config_fetch_recurse_submodules(int value)
config_fetch_recurse_submodules = value;
}
+/* check if the given prefix is inside an uninitialized submodule */
+void check_prefix_inside_submodule(const char *prefix)
+{
+ const char *work_tree = get_git_work_tree();
+ if (work_tree) {
+ int pos;
+ const struct cache_entry *in_submodule = NULL;
+
+ if (read_cache() < 0)
+ die("index file corrupt");
+ pos = cache_name_pos(prefix, strlen(prefix));
+ /*
+ * gitlinks are recored with no ending '/' in the index,
+ * but the prefix has an ending '/', so we will never find
+ * an exact match, but always the position where we'd
+ * insert the prefix.
+ */
+ if (pos < 0) {
+ const struct cache_entry *ce;
+ int len = strlen(prefix);
+ /* Check the previous position */
+ pos = (-1 - pos) - 1;
+ ce = active_cache[pos];
+ if (ce->ce_namelen < len)
+ len = ce->ce_namelen;
+ if (!memcmp(ce->name, prefix, len))
+ in_submodule = ce;
+ } else
+ /* This case cannot happen because */
+ die("BUG: prefixes end with '/', but we do not record ending slashes in the index");
+
+ if (in_submodule)
+ die(_("command from inside unpopulated submodule '%s' not supported."), in_submodule->name);
+ }
+}
+
static int has_remote(const char *refname, const struct object_id *oid,
int flags, void *cb_data)
{
diff --git a/submodule.h b/submodule.h
index b7576d6f43..6b30542822 100644
--- a/submodule.h
+++ b/submodule.h
@@ -30,6 +30,7 @@ struct submodule_update_strategy {
};
#define SUBMODULE_UPDATE_STRATEGY_INIT {SM_UPDATE_UNSPECIFIED, NULL}
+extern void check_prefix_inside_submodule(const char *prefix);
int is_staging_gitmodules_ok(void);
int update_path_in_gitmodules(const char *oldpath, const char *newpath);
int remove_path_from_gitmodules(const char *path);
--
2.11.0.299.g762782ba8a