From: Junio C Hamano <gitster@pobox.com>
To: Richard Maw <richard.maw@codethink.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Some issues when trying to set up a shallow git mirror server
Date: Wed, 13 Jan 2016 09:14:10 -0800 [thread overview]
Message-ID: <xmqqlh7tpfkt.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160113113743.GF3397@logi.codethink.co.uk> (Richard Maw's message of "Wed, 13 Jan 2016 11:37:43 +0000")
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.
> 2. After the pack is transferred.
I do not think the protocol is structured to allow you to do this
easily. The reading side is expected to read thru til the end of
the stream, not stopping at the end of the packdata, IIRC.
next prev parent reply other threads:[~2016-01-13 17:14 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 [this message]
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=xmqqlh7tpfkt.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=richard.maw@codethink.co.uk \
/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.