git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff Hostetler <git@jeffhostetler.com>,
	git@vger.kernel.org, peff@peff.net,
	Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH v5 00/10] Partial clone part 2: fsck and promisors
Date: Wed, 22 Nov 2017 10:00:14 -0800	[thread overview]
Message-ID: <20171122100014.937f5902c3714e6e26e20a1b@google.com> (raw)
In-Reply-To: <xmqqy3myubpi.fsf@gitster.mtv.corp.google.com>

On Wed, 22 Nov 2017 14:25:13 +0900
Junio C Hamano <gitster@pobox.com> wrote:

> Jeff Hostetler <git@jeffhostetler.com> writes:
> 
> > From: Jeff Hostetler <jeffhost@microsoft.com>
> >
> > This is V5 of part 2 of partial clone.  This assumes V5 of part 1
> > is already present.  V5 includes minor cleanup over V4 and better
> > separates the --exclude-promisor-objects and --missing arguments.
> >
> > Part 2 is concerned with fsck, gc, initial support for dynamic
> > object fetching, and tracking promisor objects.  Jonathan Tan
> > originally developed this code.  I have moved it on top of
> > part 1 and updated it slightly.
> 
> Thanks, will replace/queue all three series.  I am getting a feeling
> that the first one is already ready for 'next', while the other two
> may want to see a bit more comments?

Yes, I think so too.

Jeff Hostetler and I noticed some issues occuring when some other Git
commands dynamically fetch objects due to the fact that those commands
and fetch-pack use overlapping object flags. At the very least, we
should look at that before it goes into next.

  reply	other threads:[~2017-11-22 18:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 21:07 [PATCH v5 00/10] Partial clone part 2: fsck and promisors Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 01/10] extension.partialclone: introduce partial clone extension Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 02/10] fsck: introduce partialclone extension Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 03/10] fsck: support refs pointing to promisor objects Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 04/10] fsck: support referenced " Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 05/10] fsck: support promisor objects as CLI argument Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 06/10] index-pack: refactor writing of .keep files Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 07/10] introduce fetch-object: fetch one promisor object Jeff Hostetler
2017-12-02 20:33   ` Christian Couder
2017-12-05 16:18     ` Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 08/10] sha1_file: support lazily fetching missing objects Jeff Hostetler
2017-12-02 18:29   ` Christian Couder
2017-12-05 16:02     ` Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 09/10] rev-list: support termination at promisor objects Jeff Hostetler
2017-11-21 21:07 ` [PATCH v5 10/10] gc: do not repack promisor packfiles Jeff Hostetler
2017-12-02 17:39   ` Christian Couder
2017-12-05 15:45     ` Jeff Hostetler
2017-11-22  5:25 ` [PATCH v5 00/10] Partial clone part 2: fsck and promisors Junio C Hamano
2017-11-22 18:00   ` Jonathan Tan [this message]
2017-11-22 21:42     ` Jonathan Tan

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=20171122100014.937f5902c3714e6e26e20a1b@google.com \
    --to=jonathantanmy@google.com \
    --cc=git@jeffhostetler.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jeffhost@microsoft.com \
    --cc=peff@peff.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).