From: Stefan Beller <stefanbeller@googlemail.com>
To: Stefan Beller <stefanbeller@googlemail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Duy Nguyen <pclouds@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
schlotter@users.sourceforge.net, Ralf.Wildenhues@gmx.de,
git@vger.kernel.org
Subject: Re: [PATCH] add warning for depth=0 in git clone.
Date: Tue, 08 Jan 2013 09:09:55 +0100 [thread overview]
Message-ID: <50EBD453.9050101@googlemail.com> (raw)
In-Reply-To: <1357632422-5686-1-git-send-email-stefanbeller@googlemail.com>
Hi,
I am struggling a little with the development process,
is a sign-off strictly required for git as it is for kernel development?
If so here would be my sign-off:
Signed-off-by: Stefan Beller <stefanbeller@googlemail.com>
This adds a warning and the previous patch adds the documentation.
However I agree to Junio, that the meaning should actually
depth=0 -> just the tip and no (0) other commits before.
depth=n -> the tip and n other commits before.
On 01/08/2013 09:07 AM, Stefan Beller wrote:
> ---
> builtin/clone.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/builtin/clone.c b/builtin/clone.c
> index ec2f75b..5e91c1e 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -818,6 +818,9 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
> remote = remote_get(option_origin);
> transport = transport_get(remote, remote->url[0]);
>
> + if (option_depth && transport->smart_options->depth < 1)
> + die(_("--depth less or equal 0 makes no sense; read manpage."));
> +
> if (!is_local) {
> if (!transport->get_refs_list || !transport->fetch)
> die(_("Don't know how to clone %s"), transport->url);
>
next prev parent reply other threads:[~2013-01-08 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:07 [PATCH] add warning for depth=0 in git clone Stefan Beller
2013-01-08 8:09 ` Stefan Beller [this message]
2013-01-08 8:14 ` Jonathan Nieder
2013-01-08 8:12 ` Jonathan Nieder
2013-01-09 0:57 ` Duy Nguyen
2013-01-09 2:53 ` On --depth=funny value Junio C Hamano
2013-01-09 4:18 ` Duy Nguyen
2013-01-09 5:19 ` Junio C Hamano
2013-01-09 14:12 ` Duy Nguyen
2013-01-09 14:59 ` Duy Nguyen
2013-01-09 21:38 ` Stefan Beller
2013-01-11 3:30 ` [PATCH 1/2] fetch, upload-pack: add --no-shallow for infinite depth Nguyễn Thái Ngọc Duy
2013-01-11 3:30 ` [PATCH 2/2] upload-pack: fix off-by-one depth calculation in shallow clone Nguyễn Thái Ngọc Duy
2013-01-11 4:26 ` Junio C Hamano
2013-01-11 3:55 ` [PATCH 1/2] fetch, upload-pack: add --no-shallow for infinite depth Junio C Hamano
2013-01-11 9:05 ` [PATCH v2 1/3] fetch: add --unshallow for turning shallow repo into complete one Nguyễn Thái Ngọc Duy
2013-01-11 9:05 ` [PATCH v2 2/3] upload-pack: fix off-by-one depth calculation in shallow clone Nguyễn Thái Ngọc Duy
2013-01-11 9:05 ` [PATCH v2 3/3] fetch: elaborate --depth action Nguyễn Thái Ngọc Duy
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=50EBD453.9050101@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=schlotter@users.sourceforge.net \
/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.