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

Re: [PATCH] git-clone.txt: document that pushing from a shallow clone may work

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 4, 2009, 11:11 UTC
Message-ID
<alpine.DEB.1.00.0903041209070.8549@intel-tinevez-2-302>
In-Reply-To
<7vvdqp5zx9.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, 4 Mar 2009, Junio C Hamano wrote:
Show 5 quoted lines
> Isn't the rule more or less like:
> 
>     If your shallow repository's history does not extend long enough and
>     the other repository forked before your truncated history, wyou cannot
>     compute the common ancestor and you cannot push out.
Exactly.

Back when I wrote the shallow code, I meant to investigate how to detect that condition, and fail gracefully (i.e. with a meaningful error message).

IMHO that is more needed than documentation changes, as it affects more users ;-)

But in the meantime, I had no use for shallow clones, and kind of hoped that it would become somebody else's itch.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 11 in “pushing from a shallow repo allowed?”
  1. Joey HessFeb 12, 2009
  2. Mikael MagnussonFeb 16, 2009
  3. git-clone.txt: document that pushing from a shallow clone may workAdeodato Simó, Mar 3, 2009
  4. Johannes SixtMar 3, 2009
  5. Adeodato SimóMar 3, 2009
  6. Jay SoffianMar 3, 2009
  7. Adeodato SimóMar 4, 2009
  8. Junio C HamanoMar 4, 2009
  9. Johannes SchindelinMar 4, 2009
  10. Junio C HamanoMar 5, 2009
  11. Adeodato SimóMar 4, 2009

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.