* "git clone --depth <depth>" producing history with <depth + 1> commits? @ 2009-03-26 17:00 Sebastian Pipping 2009-04-01 19:39 ` Sebastian Pipping 0 siblings, 1 reply; 6+ messages in thread From: Sebastian Pipping @ 2009-03-26 17:00 UTC (permalink / raw) To: git Hello! Is "git clone --depth 1 <ropository>" expected to give a history with 2 commits? "--depth 2" gives 3 commits, "--depth 0" all. Is that by design or a bug? Sebastian ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "git clone --depth <depth>" producing history with <depth + 1> commits? 2009-03-26 17:00 "git clone --depth <depth>" producing history with <depth + 1> commits? Sebastian Pipping @ 2009-04-01 19:39 ` Sebastian Pipping 2009-04-02 1:04 ` Johannes Schindelin 0 siblings, 1 reply; 6+ messages in thread From: Sebastian Pipping @ 2009-04-01 19:39 UTC (permalink / raw) To: git Sebastian Pipping wrote: > Is "git clone --depth 1 <ropository>" expected to give a history > with 2 commits? "--depth 2" gives 3 commits, "--depth 0" all. > > Is that by design or a bug? Anyone? Is "git clone --depth 1 <ropository>" really supposed to produce a history holding _two_ commits? Why so? Sebastian ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "git clone --depth <depth>" producing history with <depth + 1> commits? 2009-04-01 19:39 ` Sebastian Pipping @ 2009-04-02 1:04 ` Johannes Schindelin 2009-04-02 1:19 ` Sebastian Pipping 2009-04-02 2:33 ` Junio C Hamano 0 siblings, 2 replies; 6+ messages in thread From: Johannes Schindelin @ 2009-04-02 1:04 UTC (permalink / raw) To: Sebastian Pipping; +Cc: git Hi, On Wed, 1 Apr 2009, Sebastian Pipping wrote: > Sebastian Pipping wrote: > > Is "git clone --depth 1 <ropository>" expected to give a history > > with 2 commits? "--depth 2" gives 3 commits, "--depth 0" all. > > > > Is that by design or a bug? > > 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_. Ciao, Dscho ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "git clone --depth <depth>" producing history with <depth + 1> commits? 2009-04-02 1:04 ` Johannes Schindelin @ 2009-04-02 1:19 ` Sebastian Pipping 2009-04-02 2:33 ` Junio C Hamano 1 sibling, 0 replies; 6+ messages in thread From: Sebastian Pipping @ 2009-04-02 1:19 UTC (permalink / raw) To: Johannes Schindelin; +Cc: git Johannes Schindelin wrote: >> 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "git clone --depth <depth>" producing history with <depth + 1> commits? 2009-04-02 1:04 ` Johannes Schindelin 2009-04-02 1:19 ` Sebastian Pipping @ 2009-04-02 2:33 ` Junio C Hamano 2009-04-02 11:00 ` Johannes Schindelin 1 sibling, 1 reply; 6+ messages in thread From: Junio C Hamano @ 2009-04-02 2:33 UTC (permalink / raw) To: Johannes Schindelin; +Cc: Sebastian Pipping, git Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > On Wed, 1 Apr 2009, Sebastian Pipping wrote: > >> Sebastian Pipping wrote: >> > Is "git clone --depth 1 <ropository>" expected to give a history >> > with 2 commits? "--depth 2" gives 3 commits, "--depth 0" all. >> > >> > Is that by design or a bug? >> >> 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? But then you can error out upon such a request. > After all, if you want to clone, you want to clone at least _something_. I am a bit puzzled by your logic. If one is requested, shouldn't you give only one and not two? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: "git clone --depth <depth>" producing history with <depth + 1> commits? 2009-04-02 2:33 ` Junio C Hamano @ 2009-04-02 11:00 ` Johannes Schindelin 0 siblings, 0 replies; 6+ messages in thread From: Johannes Schindelin @ 2009-04-02 11:00 UTC (permalink / raw) To: Junio C Hamano; +Cc: Sebastian Pipping, git Hi, On Wed, 1 Apr 2009, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > On Wed, 1 Apr 2009, Sebastian Pipping wrote: > > > >> Sebastian Pipping wrote: > >> > Is "git clone --depth 1 <ropository>" expected to give a history > >> > with 2 commits? "--depth 2" gives 3 commits, "--depth 0" all. > >> > > >> > Is that by design or a bug? > >> > >> 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? > > But then you can error out upon such a request. Right. Or disable the shallow cloning, as is the case now. > > After all, if you want to clone, you want to clone at least > > _something_. > > I am a bit puzzled by your logic. If one is requested, shouldn't you > give only one and not two? Reading the OP again, I have to apologize: I missed the fact that there is no way to have _just_ one commit. And that is very obviously a bug. If nobody beats me to it, I will take care of it this weekend. Ciao, Dscho ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-04-02 11:02 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-03-26 17:00 "git clone --depth <depth>" producing history with <depth + 1> commits? Sebastian Pipping 2009-04-01 19:39 ` Sebastian Pipping 2009-04-02 1:04 ` Johannes Schindelin 2009-04-02 1:19 ` Sebastian Pipping 2009-04-02 2:33 ` Junio C Hamano 2009-04-02 11:00 ` Johannes Schindelin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).