Re: [PATCH v2 2/2] connect: advertized capability is not a ref

From: Stefan Beller <sbeller@google.com>
Date: Sep 2, 2016, 23:48 UTC
Message-ID: <CAGZ79ka0VvXbkR+JYJwK9oyRzcsDXDoqKXyp4F+moDc4qDuv7w@mail.gmail.com>
In-Reply-To: <20160902233547.mzgluioc7hhabalw@sigill.intra.peff.net>

On Fri, Sep 2, 2016 at 4:35 PM, Jeff King <peff@peff.net> wrote:

> I'd be more interested in the pain of this transition if there was a
> concrete use case for "hide literally all refs, but still allow
> fetches". Is that a thing that people do?
>

Not yet, I would think.

Not to derail the discussion to much, but let's talk about protocol v2 for a second:

    One of the ideas we floated around for protocol v2 would be exactly
    that: the server advertises only a small portion (could be just master
    or no branch eventually) with a capability "v2" and then the client
    selects that capability and after that there comes protocol 2.

    The advantage of this approach would be have a functional
    v1 server still running, but the meat is found only in v2: e.g. via
    v2 you can obtain all pull requests/changes or even wiki/meta
    information stuff that would be too large to advertise in v1.