All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Maw <richard.maw@codethink.co.uk>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Some issues when trying to set up a shallow git mirror server
Date: Fri, 8 Jan 2016 10:52:04 +0000	[thread overview]
Message-ID: <20160108105204.GD3397@logi.codethink.co.uk> (raw)
In-Reply-To: <CACsJy8CBj-oMTLrn8gVudhLPEixZfkwFv9BaN8LSNFvOHkqKkg@mail.gmail.com>

On Fri, Jan 08, 2016 at 05:44:30PM +0700, Duy Nguyen wrote:
> It sounds a lot like what I did with narrow clone [2] prototype. A
> narrow clone only contains enough objects for certain paths so there's
> a chance that we just don't have enough to do a proper merge. A
> server-side command was added [1] to retrieve enough objects for the
> task. If you fetch commit chain without all necessary trees and
> objects, your repo is "broken" from Git point of view and you'll need
> to do some extra work to make sure your repo is not actually broken.
> 
> [1] http://article.gmane.org/gmane.comp.version-control.git/154371
> [2] http://thread.gmane.org/gmane.comp.version-control.git/154343

Thanks for the links. I'll have a read to see how it fits together.

  reply	other threads:[~2016-01-08 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 16:54 Some issues when trying to set up a shallow git mirror server Richard Maw
2016-01-07 18:00 ` Junio C Hamano
2016-01-08 10:19   ` Richard Maw
2016-01-08 10:44     ` Duy Nguyen
2016-01-08 10:52       ` Richard Maw [this message]
2016-01-08 21:37   ` Junio C Hamano
2016-01-11 15:51     ` Richard Maw
2016-01-12 18:29       ` Junio C Hamano
2016-01-13 11:37         ` Richard Maw
2016-01-13 17:14           ` Junio C Hamano
2016-01-13 17:43             ` Richard Maw

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=20160108105204.GD3397@logi.codethink.co.uk \
    --to=richard.maw@codethink.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@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. 
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.