[PATCH v7 00/10] Make submodules work if .gitmodules is not checked out
- Date: Thu, 25 Oct 2018 18:18:03 +0200
- From: Antonio Ospite <ao2@xxxxxx>
- Subject: [PATCH v7 00/10] Make submodules work if .gitmodules is not checked out
this series teaches git to try and read the .gitmodules file from the
index (:.gitmodules) or from the current branch (HEAD:.gitmodules) when
the file is not readily available in the working tree.
This can be used, together with sparse checkouts, to enable submodule
usage with programs like vcsh which manage multiple repositories with
their working trees sharing the same path.
In the previous series there were some comments about not using the enum
in patch 8, but I decided to leave the code as it was as I still think
that it make sense to use an enum there, and have the default value
unnamed; during the discussion I pointed out that other code in git do
In this series I am addressing the comments by Stefan Beller about the
tests in patch 9.
If the new tests look OK, I'd say we try moving the series to "next" and
see what happens?
I am available to address any further concerns in follow-up patches.
v6 of the series is here:
v5 of the series is here:
v4 of the series is here:
v3 of the series is here:
v2 of the series is here:
v1 of the series, with some background info, is here:
Changes since v6:
* Renamed t7416-submodule-sparse-gitmodules.sh to
t7418-submodule-sparse-gitmodules.sh because t7416 was already
taken. This has been already taken care of by Junio in "pu".
* Improved tests in t7418: now, instead of just testing the return
value of "git submodule ..." commands when .gitmodules is not in the
working tree, the actual use case is checked in each test, with pre-
Antonio Ospite (10):
submodule: add a print_config_from_gitmodules() helper
submodule: factor out a config_set_in_gitmodules_file_gently function
t7411: merge tests 5 and 6
t7411: be nicer to future tests and really clean things up
submodule--helper: add a new 'config' subcommand
submodule: use the 'submodule--helper config' command
t7506: clean up .gitmodules properly before setting up new scenario
submodule: add a helper to check if it is safe to write to .gitmodules
submodule: support reading .gitmodules when it's not in the working
t/helper: add test-submodule-nested-repo-config
Makefile | 1 +
builtin/grep.c | 17 ++-
builtin/submodule--helper.c | 40 ++++++
cache.h | 2 +
git-submodule.sh | 13 +-
submodule-config.c | 68 ++++++++-
submodule-config.h | 2 +
submodule.c | 28 +++-
submodule.h | 1 +
t/helper/test-submodule-nested-repo-config.c | 30 ++++
t/helper/test-tool.c | 1 +
t/helper/test-tool.h | 1 +
t/t7411-submodule-config.sh | 141 +++++++++++++++++--
t/t7418-submodule-sparse-gitmodules.sh | 122 ++++++++++++++++
t/t7506-status-submodule.sh | 3 +-
t/t7814-grep-recurse-submodules.sh | 16 +++
16 files changed, 454 insertions(+), 32 deletions(-)
create mode 100644 t/helper/test-submodule-nested-repo-config.c
create mode 100755 t/t7418-submodule-sparse-gitmodules.sh
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?