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

Re: Fwd: Failed shallow submodule clone for fixed SHA1 falls back to checking out HEAD

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Apr 18, 2017, 19:18 UTC
Message-ID
<bf1bd6e4-e099-53b6-428a-85d1e02ee75c@gmail.com>
In-Reply-To
<CAGZ79kZy1rBUaF1XbUOPUxDPzT1FwCp92jbbiO4RX3aiCoNkxQ@mail.gmail.com>
On 2017-04-18 21:12, Stefan Beller wrote:
Show 5 quoted lines
>> Wouldn't it make more sense to unshallow the submodule clone in this case and checkout the configured commit 2aa4cce7d7fd46164030f2b4d244c4b89e77f722 afterwards?
> 
> If I remember correctly the conclusion of the discussion at the time
> was that people are more interested in "less data" rather than
> "correct data" because otherwise you would not have asked for shallow.

I do believe this is an awkward choice. What does it help to get less data if it's the wrong data?

-- 
Sebastian Schuberth
Previous: Stefan Beller
Message 3 of 3 in “Failed shallow submodule clone for fixed SHA1 falls back to checking out HEAD”
  1. Sebastian SchuberthApr 18, 2017
  2. Fwd: Failed shallow submodule clone for fixed SHA1 falls back to checking out HEADStefan Beller, Apr 18, 2017
  3. Sebastian SchuberthApr 18, 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.