From: Jonathan Tan <jonathantanmy@google.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org, peartben@gmail.com,
Christian Couder <christian.couder@gmail.com>,
git@jeffhostetler.com
Subject: Re: RFC: Design and code of partial clones (now, missing commits and trees OK)
Date: Thu, 28 Sep 2017 17:53:52 -0700 [thread overview]
Message-ID: <20170928175352.9a490564d47172568ea2f416@google.com> (raw)
In-Reply-To: <20170915134343.3814dc38@twelve2.svl.corp.google.com>
On Fri, 15 Sep 2017 13:43:43 -0700
Jonathan Tan <jonathantanmy@google.com> wrote:
> For those interested in partial clones and/or missing objects in repos,
> I've updated my original partialclone patches to not require an explicit
> list of promises. Fetch/clone still only permits exclusion of blobs, but
> the infrastructure is there for a local repo to support missing trees
> and commits as well.
>
> They can be found here:
>
> https://github.com/jonathantanmy/git/tree/partialclone2
I've pushed a new version:
https://github.com/jonathantanmy/git/tree/partialclone3
Besides some small changes as requested by comments on the GitHub
repository, I've also updated the code to do the following:
- clarified terminology - in particular, I've tried to avoid
"promised", only using "promisor object" to denote objects that the
local repo knows that the promisor remote has, whether the local repo
has it or not
- restored bulk checkout functionality (so now you can clone with
--blob-max-bytes=0)
- a fix to fetch-pack to restore a global flag after it uses it, so
commands like "git log -S" still work (but to test this, I used
--blob-max-bytes=200000 with the Git repository, because batch
fetching is not implemented for commands like these)
In its current form, the code is already useful for situations like:
- a large repository with many blobs in which the client only needs to
checkout, at most, and does not need to search through history
locally, and
- a repository with a few large blobs, where the client still can
search through history as long as the client is online
next prev parent reply other threads:[~2017-09-29 0:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 20:43 RFC: Design and code of partial clones (now, missing commits and trees OK) Jonathan Tan
2017-09-19 5:51 ` Junio C Hamano
2017-09-21 17:57 ` Jeff Hostetler
2017-09-21 22:42 ` Jonathan Tan
2017-09-22 21:02 ` Jeff Hostetler
2017-09-22 22:49 ` Jonathan Tan
2017-09-26 15:26 ` Michael Haggerty
2017-09-29 20:21 ` Jonathan Tan
2017-09-21 17:59 ` RFC: Design and code of partial clones (now, missing commits and trees OK) (part 2/3) Jeff Hostetler
2017-09-21 22:51 ` Jonathan Tan
2017-09-22 21:19 ` Jeff Hostetler
2017-09-22 22:52 ` Jonathan Tan
2017-09-26 14:03 ` Jeff Hostetler
2017-09-21 18:00 ` RFC: Design and code of partial clones (now, missing commits and trees OK) (part 3) Jeff Hostetler
2017-09-21 23:04 ` Jonathan Tan
2017-09-22 21:32 ` Jeff Hostetler
2017-09-22 22:58 ` Jonathan Tan
2017-09-26 14:25 ` Jeff Hostetler
2017-09-26 17:32 ` Jonathan Tan
2017-09-29 0:53 ` Jonathan Tan [this message]
2017-09-29 2:03 ` RFC: Design and code of partial clones (now, missing commits and trees OK) 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=20170928175352.9a490564d47172568ea2f416@google.com \
--to=jonathantanmy@google.com \
--cc=christian.couder@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=peartben@gmail.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.
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).