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

Re: [RFC 0/4] Shallow clones with on-demand fetch

From
Stefan Beller <sbeller@google.com>
Date
Mar 6, 2017, 20:01 UTC
Message-ID
<CAGZ79kZ1K-4PJC45nSZLX3m+FrYrsz8yy__dpwmMd8niRZX_dQ@mail.gmail.com>
In-Reply-To
<c8788f30-263b-c96a-239d-940743b96b53@google.com>
On Mon, Mar 6, 2017 at 11:16 AM, Jonathan Tan <jonathantanmy@google.com> wrote:
> [1] <20170113155253.1644-1-benpeart@microsoft.com> (you can search for
> emails by Message ID in online archives like https://public-inbox.org/git if
> you don't already have them)
Not just search, but the immediate lookup is
 https://public-inbox.org/git/<message-id>
so
 https://public-inbox.org/git/20170113155253.1644-1-benpeart@microsoft.com
> [2] <cover.1487984670.git.jonathantanmy@google.com>
and
  https://public-inbox.org/git/cover.1487984670.git.jonathantanmy@google.com
Previous: Jonathan Tan
Message 9 of 9 in “[RFC 0/4] Shallow clones with on-demand fetch”
  1. Mark ThomasMar 4, 2017
  2. 3/4 upload-pack: Send all commits if client requests on-demandMark Thomas, Mar 4, 2017
  3. 4/4 clone: Request on-demand shallow clonesMark Thomas, Mar 4, 2017
  4. 1/4 upload-file: Add upload-file commandMark Thomas, Mar 4, 2017
  5. 2/4 on-demand: Fetch missing files from remoteMark Thomas, Mar 4, 2017
  6. Junio C HamanoMar 6, 2017
  7. Jeff KingMar 7, 2017
  8. Jonathan TanMar 6, 2017
  9. Stefan BellerMar 6, 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.