git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "ankostis" <ankostis@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Would it make sense to add `--depth=0` feature?
Date: Sat, 12 Aug 2017 10:23:23 +0100	[thread overview]
Message-ID: <F3E6E31F66C645D8B86BCB8B6E639BC3@PhilipOakley> (raw)
In-Reply-To: CA+dhYEXDsgnmKTf9OW+_QTPkcVkfm99ffWOYdum7uUTnvaaCeA@mail.gmail.com

From: "ankostis" <ankostis@gmail.com>
> Would it be feasible/sensical to support clone/fetch with --depth=0?
> The point is to download the tags/commit objects but not the actual
> trees and blobs,
> creating a "ledger" acting as a promise for the remote'e repo content?
>
> Is there some estimation of the effort required to do such thing?
>
> Best,
>  Kostis

I think that the desire is reasonable, but that it doesn't match the shallow 
clone idea. I think you are asking for a 'Narrow' clone where there is some 
form of exclusion of the blobs and trees that attach to the commit objects 
(at the various depths of commit graph walking).

There is some work on-going at the moment for various types of sparse 
download (look for "lazy objects" and "partial clone" on the list archive 
https://public-inbox.org/git/?q=) to see if you can help with ensuring that 
the methods will be useful to you.
(I'm interested too!)
--
Philip 


      reply	other threads:[~2017-08-12  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 23:23 Would it make sense to add `--depth=0` feature? ankostis
2017-08-12  9:23 ` Philip Oakley [this message]

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=F3E6E31F66C645D8B86BCB8B6E639BC3@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=ankostis@gmail.com \
    --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.
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).