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

Re: "git clone --depth <depth>" producing history with <depth + 1> commits?

From
SPSebastian Pipping <webmaster@hartwork.org>
Date
Apr 2, 2009, 01:19 UTC
Message-ID
<49D4128D.7000803@hartwork.org>
In-Reply-To
<alpine.DEB.1.00.0904020303320.10279@pacific.mpi-cbg.de>
Johannes Schindelin wrote:
Show 7 quoted lines
>> Anyone?  Is "git clone --depth 1 <ropository>" really supposed to 
>> produce a history holding _two_ commits?  Why so?
> 
> Because storing _no_ commit (according to you, that should happen with 
> --depth=0) would make no sense?
> 
> After all, if you want to clone, you want to clone at least _something_.
I'm aware you need one commit at least.

I didn't think of several branches before. I guess that's resolving the core of my question.

Sebastian
Previous: Johannes SchindelinNext: Junio C Hamano
Message 4 of 6 in “"git clone --depth <depth>" producing history with <depth + 1> commits?”
  1. Sebastian PippingMar 26, 2009
  2. Sebastian PippingApr 1, 2009
  3. Johannes SchindelinApr 2, 2009
  4. Sebastian PippingApr 2, 2009
  5. Junio C HamanoApr 2, 2009
  6. Johannes SchindelinApr 2, 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.