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

Re: [PATCH] clone,fetch: explain the shallow-clone option a little more clearly

From
Duy Nguyen <pclouds@gmail.com>
Date
Dec 6, 2016, 09:34 UTC
Message-ID
<CACsJy8Cy+iWw4NhR7B_fZhBMMYt2QxdMeFsC=++LLnrTLNWfKw@mail.gmail.com>
In-Reply-To
<xmqq37i25iy5.fsf@gitster.mtv.corp.google.com>
On Tue, Dec 6, 2016 at 1:28 AM, Junio C Hamano <gitster@pobox.com> wrote:
> I however offhand do not think the feature can be used to make the
> repository shallower

I'm pretty sure it can, though it's a waste because you should be able to shorten your history without talking to a remote server. But that no-remote shortening is not implemented yet. And you probably want an option to check with remote anyway to make sure the part you cut out is available there, no history will be lost.

-- 
Duy
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 5 in “clone,fetch: explain the shallow-clone option a little more clearly”
  1. clone,fetch: explain the shallow-clone option a little more clearlyAlex Henrie, Dec 4, 2016
  2. Junio C HamanoDec 5, 2016
  3. Duy NguyenDec 6, 2016
  4. Junio C HamanoDec 6, 2016
  5. Duy NguyenDec 7, 2016

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.