Hi, On Wed, 1 Apr 2009, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
