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

[PATCH v2 0/2] Advice upon clone --recurse-submodules --reference

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Dec 2, 2019, 19:57 UTC
Message-ID
<cover.1575316490.git.jonathantanmy@google.com>
In-Reply-To
<cover.1574731649.git.jonathantanmy@google.com>

Thanks everyone! Here's an updated v2 following Peff's suggestions on how to write the advice part.

Making submodule.alternateErrorStrategy default to 'info' is reasonable, but I don't know how much it matters in practice - here, submodule.alternateLocation was set because of "clone --recurse-submodules --reference", which also sets submodule.alternateErrorStrategy. I don't know when submodule.alternateLocation would ever be set alone, but then again, I'm not very familiar with this part. I've left that alone for now.

Jonathan Tan (2):
  Doc: explain submodule.alternateErrorStrategy
  submodule--helper: advise on fatal alternate error
 Documentation/config/advice.txt    |  3 +++
 Documentation/config/submodule.txt |  4 +++-
 advice.c                           |  2 ++
 advice.h                           |  1 +
 builtin/submodule--helper.c        | 10 ++++++++++
 5 files changed, 19 insertions(+), 1 deletion(-)
-- 
2.24.0.393.g34dc348eaf-goog
Previous: Jeff KingNext: Jonathan Tan
Message 7 of 11 in “Advice upon clone --recurse-submodules --reference”
  1. 0/2 Advice upon clone --recurse-submodules --referenceJonathan Tan, Nov 26, 2019
  2. 1/2 Doc: explain submodule.alternateErrorStrategyJonathan Tan, Nov 26, 2019
  3. Jeff KingNov 27, 2019
  4. Junio C HamanoNov 27, 2019
  5. 2/2 submodule--helper: advise on fatal alternate errorJonathan Tan, Nov 26, 2019
  6. Jeff KingNov 27, 2019
  7. 0/2 Advice upon clone --recurse-submodules --referenceJonathan Tan, Dec 2, 2019
  8. 1/2 Doc: explain submodule.alternateErrorStrategyJonathan Tan, Dec 2, 2019
  9. 2/2 submodule--helper: advise on fatal alternate errorJonathan Tan, Dec 2, 2019
  10. Jeff KingDec 3, 2019
  11. Junio C HamanoDec 3, 2019

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.