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

Re: Bug in shallow clone?

From
Dennis Kaarsemaker <dennis@kaarsemaker.net>
Date
May 28, 2014, 14:29 UTC
Message-ID
<1401287364.3329.0.camel@seahawk>
In-Reply-To
<CACsJy8AmxNDcxtT0XiR8-j=sO0Eo8t5E2apf5SuYU6+EogNm7w@mail.gmail.com>
On wo, 2014-05-28 at 21:16 +0700, Duy Nguyen wrote:
Show 15 quoted lines
> On Wed, May 28, 2014 at 9:02 PM, Thomas Kieffer <ThomasKieffer@web.de> wrote:
> > I then clone the bare repository with --depth 1.
> >
> > git clone file:///path/to/bare.git ./clone --depth 1
> >
> > It always returns the last two commits. If I specify --depth 2 it returns
> > the last 3 commits.
> >
> > If I use --depth 1 on a Github repository it works as expected.
> >
> > Am I doing something wrong or is it really a bug?
> 
> Depth calculation has been corrected lately. It depends on your
> version, maybe it's older than 1.8.2? If it's the latest, we screwed
> something up again..
2.0.0-rc4 does this correctly.
-- 
Dennis Kaarsemaker
http://www.kaarsemaker.net
Previous: Duy Nguyen
Message 3 of 3 in “Bug in shallow clone?”
  1. Thomas KiefferMay 28, 2014
  2. Duy NguyenMay 28, 2014
  3. Dennis KaarsemakerMay 28, 2014

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.