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 15, 2013, 15:31 UTC
Message-ID
<7voba3dem1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8DELmhBwBCk9hmg4EpQxGeCRDPaSEr5rYp=CiMjq8j54Q@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 12 quoted lines
> On Mon, Jul 15, 2013 at 8:01 AM, Duy Nguyen <pclouds@gmail.com> wrote:
>>> 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.
>>>
>>
>> Hmm.. right. And the receiver needs to setup proper graft to seal the
>> shallow bottom. So it's really not safe to do pushing from a shallow
>> repo without 52fed6e
>
> Because this makes pushing from a shallow repo fall into "mostly
> works" category, I withdraw this patch.

Yeah, "reliably fails when it shouldn't" may be safer than before that patch, but the fact that you cannot push from a shallow one still remains, so we probably shouldn't tell the users to use it.

Previous: Duy NguyenNext: Junio C Hamano
Message 10 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.