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

Re: [PATCH] git-clone.txt: remove the restriction on pushing from a shallow clone

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 14, 2013, 18:52 UTC
Message-ID
<7vfvvhgeif.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8ATX8aJJ40sF5XSoVpy=X1ZTLj5qpthrTQ52fv40QNn7w@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 16 quoted lines
> On Sun, Jul 14, 2013 at 4:25 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Hi,
>>
>> Nguyễn Thái Ngọc Duy wrote:
>>
>>> Since 52fed6e (receive-pack: check connectivity before concluding "git
>>> push" - 2011-09-02), receive-pack is prepared to deal with broken
>>> push, a shallow push can't cause any corruption. Update the document
>>> to reflect that.
>>
>> Hmm, what happens when pushing to servers without that commit?  Do you
>> think it should be applied to Debian squeeze for server operators that
>> haven't upgraded yet to the current stable release?
>
> This is pushing _from_ a shallow repo, where the sender repo's old
> objects is a subset of the receiver's.

The "subset" assumption does not necessarily hold, does it? The receiver may have rewound its tips and pruned since then.

Also, the sender may have cloned from the receiver (fully) and then fetched a different history shallowly from elsewhere. The receiver may have no commit on that history, including the shallow-bottom.

Previous: Duy NguyenNext: Duy Nguyen
Message 7 of 11 in “git-clone.txt: remove the restriction on pushing from a shallow clone”
  1. git-clone.txt: remove the restriction on pushing from a shallow cloneNguyễn Thái Ngọc Duy, Jul 12, 2013
  2. Junio C HamanoJul 12, 2013
  3. Junio C HamanoJul 12, 2013
  4. Duy NguyenJul 12, 2013
  5. Jonathan NiederJul 13, 2013
  6. Duy NguyenJul 14, 2013
  7. Junio C HamanoJul 14, 2013
  8. Duy NguyenJul 15, 2013
  9. Duy NguyenJul 15, 2013
  10. Junio C HamanoJul 15, 2013
  11. Revert "git-clone.txt: remove the restriction on pushing from a shallow clone"Junio C Hamano, Jul 15, 2013

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.