From: Stefan Beller <stefanbeller@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
schlotter@users.sourceforge.net, Ralf.Wildenhues@gmx.de,
git@vger.kernel.org
Subject: Re: On --depth=funny value
Date: Wed, 09 Jan 2013 22:38:54 +0100 [thread overview]
Message-ID: <50EDE36E.8030700@googlemail.com> (raw)
In-Reply-To: <7vy5g383sy.fsf_-_@alter.siamese.dyndns.org>
On 01/09/2013 03:53 AM, Junio C Hamano wrote:
> Can people sanity check the reasoning outlined here? Anything I
> missed?
>
> The above outline identifies three concrete tasks that different
> people can tackle more or less independently, each with updated
> code, documentation and test:
>
> 1. "git fetch --unshallow" that gives a pretty surface on Duy's
> "--depth=inf";
>
> 2. Making "git fetch" and "git clone" die on "--depth=0" or
> "--depth=-4";
>
> 3 Updating "upload-pack" to count correctly.
>
> I'll refrain from saying "Any takers?" for now.
Sorry for answering with delay, I am just contributing to git in my
spare time.
So if I understood Duy correctly, he is going to solve 1. and 3 by his
patches.
I'll try to come up with a solution for 2. within the next days.
next prev parent reply other threads:[~2013-01-09 21:39 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
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 [this message]
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=50EDE36E.8030700@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.