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 12, 2013, 05:53 UTC
Message-ID
<7v38rkpbmr.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1373607462-12836-1-git-send-email-pclouds@gmail.com>
Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:
Show 9 quoted lines
> The document says one cannot push from a shallow clone. But that is
> not true (maybe it was at some point in the past). The client does not
> stop such a push nor does it give any indication to the receiver that
> this is a shallow push. If the receiver accepts it, it's in.
>
> 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.
Err, what are these lines in builtin/receive-pack.c doing, then?
        int cmd_receive_pack(int argc, const char **argv, const char *prefix)
        {
                ...
                setup_path();
                if (!enter_repo(dir, 0))
                        die("'%s' does not appear to be a git repository", dir);
                if (is_repository_shallow())
                        die("attempt to push into a shallow repository");
                ...
Previous: Nguyễn Thái Ngọc DuyNext: Junio C Hamano
Message 2 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.