From: Sebastian Pipping <webmaster@hartwork.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: "git clone --depth <depth>" producing history with <depth + 1> commits?
Date: Thu, 02 Apr 2009 03:19:09 +0200 [thread overview]
Message-ID: <49D4128D.7000803@hartwork.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0904020303320.10279@pacific.mpi-cbg.de>
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
next prev parent reply other threads:[~2009-04-02 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-04-02 2:33 ` Junio C Hamano
2009-04-02 11:00 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D4128D.7000803@hartwork.org \
--to=webmaster@hartwork.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).