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

Re: [PATCH v2] submodule: explain first attempt failure clearly

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 13, 2019, 23:13 UTC
Message-ID
<xmqqmulycqr0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190313175738.252961-1-jonathantanmy@google.com>
Jonathan Tan <jonathantanmy@google.com> writes:
> It is additional to what fetch prints. To make it clearer, I have
> removed all mentions of "additional" from the commit message. But right
> now I'm not sure if that whole section is important (since what happens
> can be deduced quite easily by reading the fewer than 10 lines of code).
Hmph, perhaps.  It was lot easier to follow, at least to me, though ;-)
> If you mean a recommendation to the repository administrator, I guess we
> can recommend that their HEAD points to something, even if it's just a
> single orphan commit with a .txt file explaining what's going on.
Yeah, that might make sense, too.
Previous: Jonathan Tan
Message 4 of 4 in “submodule: explain first attempt failure clearly”
  1. submodule: explain first attempt failure clearlyJonathan Tan, Mar 12, 2019
  2. Junio C HamanoMar 13, 2019
  3. submodule: explain first attempt failure clearlyJonathan Tan, Mar 13, 2019
  4. Junio C HamanoMar 13, 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.