From: Jonathan Nieder <jrnieder@gmail.com>
To: Stefan Beller <stefanbeller@googlemail.com>
Cc: schlotter@users.sourceforge.net, gitster@pobox.com,
Ralf.Wildenhues@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH] git clone depth of 0 not possible.
Date: Mon, 7 Jan 2013 22:28:11 -0800 [thread overview]
Message-ID: <20130108062811.GA3131@elie.Belkin> (raw)
In-Reply-To: <1357581996-17505-1-git-send-email-stefanbeller@googlemail.com>
Stefan Beller wrote:
> Currently it is not possible to have a shallow depth of
> just 0, i.e. only one commit in that repository after cloning.
> The minimum number of commits is 2, caused by depth=1.
Sounds buggy. Would anything break if we were to make --depth=1 mean
"1 deep, including the tip commit"?
next prev parent reply other threads:[~2013-01-08 6:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:06 [PATCH] git clone depth of 0 not possible Stefan Beller
2013-01-07 18:06 ` [PATCH] Documentation on depth option in git clone Stefan Beller
2013-01-08 6:28 ` Jonathan Nieder [this message]
2013-01-08 6:54 ` [PATCH] git clone depth of 0 not possible Junio C Hamano
2013-01-08 7:36 ` Junio C Hamano
2013-01-08 8:19 ` Junio C Hamano
2013-01-08 14:28 ` Duy Nguyen
2013-01-08 14:32 ` Stefan Beller
2013-01-08 14:45 ` Duy Nguyen
2013-01-08 17:24 ` Junio C Hamano
2013-01-08 7:38 ` Duy Nguyen
2013-01-08 8:05 ` Junio C Hamano
2013-05-28 9:18 ` Matthijs Kooijman
2013-05-28 16:28 ` Jonathan Nieder
2013-05-28 16:31 ` Jonathan Nieder
2013-05-28 16:34 ` Matthijs Kooijman
2013-05-28 16:58 ` Jonathan Nieder
2013-05-28 17:04 ` Junio C Hamano
2013-05-30 8:23 ` Matthijs Kooijman
2013-06-02 19:14 ` Junio C Hamano
2013-07-09 13:35 ` Matthijs Kooijman
2013-07-11 10:57 ` Matthijs Kooijman
2013-07-11 11:25 ` [PATCH 1/3] upload-pack: Remove a piece of dead code Matthijs Kooijman
2013-07-11 11:25 ` [PATCH 2/3] upload-pack: Introduce new "fixed-off-by-one-depth" server feature Matthijs Kooijman
2013-07-11 11:25 ` [PATCH 3/3] fetch-pack: Request fixed-off-by-one-depth when available Matthijs Kooijman
2013-07-11 12:08 ` [PATCH 1/3] upload-pack: Remove a piece of dead code Duy Nguyen
2013-07-11 15:49 ` Junio C Hamano
2013-01-08 7:33 ` [PATCH] git clone depth of 0 not possible Duy Nguyen
2013-01-08 7:37 ` Junio C Hamano
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=20130108062811.GA3131@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schlotter@users.sourceforge.net \
--cc=stefanbeller@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.