All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Maw <richard.maw@codethink.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Some issues when trying to set up a shallow git mirror server
Date: Wed, 13 Jan 2016 17:43:32 +0000	[thread overview]
Message-ID: <20160113174331.GI3397@logi.codethink.co.uk> (raw)
In-Reply-To: <xmqqlh7tpfkt.fsf@gitster.mtv.corp.google.com>

On Wed, Jan 13, 2016 at 09:14:10AM -0800, Junio C Hamano wrote:
> Richard Maw <richard.maw@codethink.co.uk> writes:
> 
> > 1.  Before any "want" requests.
> >
> >     This would also let you extend ls-remote to let it display ancestry.
> >
> >     This is complicated by the fact that normally the client responds
> >     with which features it supports in the first "want",
> >     so the sender would have to support "check-ff N O <FEATURES>"
> >     if it advertised "ancestry-check".
> 
> Yes, that sounds like a good thing.  Actually, ls-remote is a
> degenerated case of fetch that sends 0 "want" requests, so the above
> may be identical to what I suggested in the message you are
> responding to.

Thanks. I've got a good idea of what I'd need to do now.

      reply	other threads:[~2016-01-13 17:43 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160113174331.GI3397@logi.codethink.co.uk \
    --to=richard.maw@codethink.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.