Thread (15 messages) flat view 15 messages, 2 authors, 2016-06-15

Re: [RFC/PATCH v3 3/3] archive.c: add basic support for submodules

From: Lars Hjemli <hidden>
Date: 2016-06-15 22:46:01

On Fri, Jan 23, 2009 at 00:44, Johannes Schindelin
[off-list ref] wrote:
On Thu, 22 Jan 2009, Lars Hjemli wrote:
quoted
The new --submodules option is used to trigger inclusion of checked out
submodules in the archive.

The implementation currently does not verify that the submodule has been
registered as 'interesting' in .git/config, neither does it resolve the
currently checked out submodule HEAD but instead uses the commit SHA1
recorded in the gitlink entry to identify the submodule root tree.
Please understand that I skipped the rest of the patch.
That's too bad, I hoped on some feedback from you on the part of the
commit message which you didn't quote:
quoted
The plan is to fix these limitations by extending --submodules to allow
certain flags/options:
a|c|r     include any|checked out|registered submodules
H         resolve submodule HEAD to decide which tree to include
g:<name>  only include submodules in group <name>

The syntax would then become '--submodules[=[a|c|r][H][g:<name>]]' and
group membership could be specified in .git/config and/or .gitmodules.
The current behavior would then match '--submodules=c' (which might be a
sensible default when only --submodules is specified).
Wouldn't such an option address your concern about the
consistency/semantics of the --submodules operation?

--
larsh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help