git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] clone: record submodule alternates when not recursing

From
Stefan Beller <sbeller@google.com>
Date
Apr 11, 2017, 19:46 UTC
Message-ID
<20170411194616.4963-1-sbeller@google.com>
The meat is in the second patch:
    The commit 31224cbdc7 (clone: recursive and reference option triggers
    submodule alternates, 2016-08-17) argued for any further `submodule update`
    to respect the initial setup. This is not the case if you only pass
    '--reference[-if-able]' to the initial clone without instructing to
    recurse into submodules.
    
    If there are submodules however the user is likely to later run
    a 'submodule update --init' to obtain the submodules. In this case we
    also want to have the references available.
The first patch produces a nice helper function and some refactoring.

Thanks, Stefan

Stefan Beller (2):
  submodule.c: add has_submodules to check if we have any submodules
  clone: remember references for submodules even when not recursing
 builtin/checkout.c          |  2 +-
 builtin/clone.c             |  8 +++--
 builtin/fetch.c             |  2 +-
 builtin/read-tree.c         |  2 +-
 builtin/submodule--helper.c |  6 ++--
 submodule.c                 | 78 +++++++++++++++++++++++++++++++++++----------
 submodule.h                 |  8 ++++-
 unpack-trees.c              |  2 +-
 8 files changed, 82 insertions(+), 26 deletions(-)
-- 
2.12.2.575.gb14f27f917
Next: Stefan Beller
Message 1 of 9 in “clone: record submodule alternates when not recursing”
  1. 0/2 clone: record submodule alternates when not recursingStefan Beller, Apr 11, 2017
  2. 1/2 submodule.c: add has_submodules to check if we have any submodulesStefan Beller, Apr 11, 2017
  3. Brandon WilliamsApr 20, 2017
  4. Stefan BellerApr 20, 2017
  5. Brandon WilliamsApr 20, 2017
  6. 2/2 clone: remember references for submodules even when not recursingStefan Beller, Apr 11, 2017
  7. Brandon WilliamsApr 20, 2017
  8. Stefan BellerApr 20, 2017
  9. Stefan BellerApr 19, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.