From: Stefan Beller <stefanbeller@googlemail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
schlotter@users.sourceforge.net, Ralf.Wildenhues@gmx.de,
git@vger.kernel.org
Subject: Re: [PATCH] git clone depth of 0 not possible.
Date: Tue, 08 Jan 2013 15:32:05 +0100 [thread overview]
Message-ID: <50EC2DE5.2050704@googlemail.com> (raw)
In-Reply-To: <CACsJy8BJ3eBv-wjq=eTzR4SeEXW2MF5k1w5SFRt7fWRU4vKb_Q@mail.gmail.com>
On 01/08/2013 03:28 PM, Duy Nguyen wrote:
> On Tue, Jan 8, 2013 at 2:36 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Speaking of --depth, I think in Git 2.0 we should fix the semantics
>> of "deepening" done with "git fetch".
>
> Speaking of 2.0, we should support depth per ref. Well we don't have
> to wait until 2.0 because we could just add shallow2 extension to the
> pack protocol. We should also apply depth to new refs when fetching
> them the first time.
>
Would this mean I could do something along?
$ git clone --since v1.8.0 git://github.com/gitster/git.git
So tags would be allowed as anchors?
next prev parent reply other threads:[~2013-01-08 14:38 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 ` [PATCH] git clone depth of 0 not possible Jonathan Nieder
2013-01-08 6:54 ` 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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EC2DE5.2050704@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).