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

Re: [PATCH/GSoC/RFC] fetch: git fetch --deepen

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 14, 2015, 22:07 UTC
Message-ID
<xmqqoanvw7v4.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CACsJy8C1nHCv0XTDYu+R8QFbG9LqjiUU7kTM1RqnzomtcoVCfw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 12 quoted lines
> On Sat, Mar 14, 2015 at 12:35 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Dongcan Jiang <dongcan.jiang@gmail.com> writes:
>>> What does (you) exactly mean in [1]? The local branch or the local
>>> remote ref?
>>
>> As this operation is not about moving _any_ refs, whether local
>> branches or remote-tracking branches, any ref that used to point at
>> commit B before you executed "fetch --deepen" would point at the
>> same commit after the command finishes.
>
> That would make it harder to implement "fetch --deepen" than the
> version that moves refs if they are updated.

The comment you are responding to was in the context of "What does the illustrated 'your' history mean? Is it a history of a single ref (if so in which repository)?" to clarify that the example was not fetching _new_ history (and with the RFC/POC design that was posted, my understanding is that deepen was meant to only deepen).

The paragraph you are reacting to is not an endorsement for that "only deepen, never advance" design. It merely is a clarification of the explanation that was in the paragraph that follows.

Show 12 quoted lines
> And I think what Dongcan
> implemented moves refs. From the user point of view, I think it's ok
> with either version, so the one that's easier to implement wins.
>
>> The "you" does not explicitly depict any ref, because the picture is
>> meant to illustrate _everything_ the repository at the receiving end
>> of "fetch" has.  It used to have two commits, A and B (and the tree
>> and blob objects necessary to complete these two commits).  After
>> deepening the history by one commit, it then will have commit A^ and
>> its trees and blobs.
>>
>>> [1] http://article.gmane.org/gmane.comp.version-control.git/212950
Previous: Duy NguyenNext: Dongcan Jiang
Message 6 of 14 in “fetch: git fetch --deepen”
  1. fetch: git fetch --deepenDongcan Jiang, Mar 13, 2015
  2. Eric SunshineMar 13, 2015
  3. Dongcan JiangMar 16, 2015
  4. Junio C HamanoMar 14, 2015
  5. Duy NguyenMar 14, 2015
  6. Junio C HamanoMar 14, 2015
  7. Dongcan JiangMar 16, 2015
  8. Duy NguyenMar 14, 2015
  9. Dongcan JiangMar 16, 2015
  10. Duy NguyenMar 17, 2015
  11. Dongcan JiangMar 17, 2015
  12. fetch: git fetch --deepenDongcan Jiang, Mar 22, 2015
  13. Eric SunshineMar 22, 2015
  14. Duy NguyenMar 22, 2015

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.