On 02/27, Jonathan Nieder wrote:
I'll make the documentation changes you suggested.
> > +deepen
> > + Request that the fetch/clone should be shallow having a commit depth of
>
> nit: s/Request/Requests/, for consistency with the others?
>
> > +relative to the remote side.
>
> What
Hi,
Brandon Williams wrote:
> Add the 'shallow' feature to the protocol version 2 command 'fetch'
> which indicates that the server supports shallow clients and deepen
> requets.
>
> Signed-off-by: Brandon Williams
> ---
> Documentation/technical/protocol-v2.txt | 67
On 02/07, Stefan Beller wrote:
> On Tue, Feb 6, 2018 at 5:12 PM, Brandon Williams wrote:
> > Add the 'shallow' feature to the protocol version 2 command 'fetch'
> > which indicates that the server supports shallow clients and deepen
> > requets.
> >
> > Signed-off-by: Brandon
On Thu, Feb 8, 2018 at 2:00 AM, Stefan Beller wrote:
>> +
>> +deepen-relative
>> + Requests that the semantics of the "deepen" command be changed
>> + to indicate that the depth requested is relative to the clients
>> + current shallow boundary, instead
On Tue, Feb 6, 2018 at 5:12 PM, Brandon Williams wrote:
> Add the 'shallow' feature to the protocol version 2 command 'fetch'
> which indicates that the server supports shallow clients and deepen
> requets.
>
> Signed-off-by: Brandon Williams
> ---
>
Add the 'shallow' feature to the protocol version 2 command 'fetch'
which indicates that the server supports shallow clients and deepen
requets.
Signed-off-by: Brandon Williams
---
Documentation/technical/protocol-v2.txt | 67 +++-
serve.c
6 matches
Mail list logo