On Thu, Jun 4, 2015 at 6:09 AM, Jeff King p...@peff.net wrote:
On Mon, Jun 01, 2015 at 10:49:45AM -0700, Stefan Beller wrote:
However the client side with builtin/fetch, builtin/fetch-pack, fetch-pack
is a bit of a mystery to me, as I cannot fully grasp the difference between
* connect.{h,c}
On Mon, Jun 01, 2015 at 10:49:45AM -0700, Stefan Beller wrote:
However the client side with builtin/fetch, builtin/fetch-pack, fetch-pack
is a bit of a mystery to me, as I cannot fully grasp the difference between
* connect.{h,c}
* remote.{h.c}
* transport.{h.c}
there. All of it seems to
On Tue, Jun 2, 2015 at 12:49 AM, Stefan Beller sbel...@google.com wrote:
However the client side with builtin/fetch, builtin/fetch-pack, fetch-pack
is a bit of a mystery to me, as I cannot fully grasp the difference between
* connect.{h,c}
* remote.{h.c}
* transport.{h.c}
there. All of it
On Wed, May 27, 2015 at 12:08 AM, Jeff King p...@peff.net wrote:
On Wed, May 27, 2015 at 02:18:18AM -0400, Jeff King wrote:
The new protocol works just like the old protocol, except for
the capabilities negotiation being before any exchange of real data.
I like this approach. [...]
So
On Tue, May 26, 2015 at 03:01:04PM -0700, Stefan Beller wrote:
Just give us something to play around with - Peff at GitMerge 2015
Sounds like something I would say.
The new protocol works just like the old protocol, except for
the capabilities negotiation being before any exchange of
On Wed, May 27, 2015 at 02:18:18AM -0400, Jeff King wrote:
The new protocol works just like the old protocol, except for
the capabilities negotiation being before any exchange of real data.
I like this approach. [...]
So now I've read through all the patches. I still like it. :)
There's
Just give us something to play around with - Peff at GitMerge 2015
This is another approach for updating the pack protocol of Git.
While in the previous attempts I tried to come up with the perfect
specification of the new protocol I realized that such an approach
doesn't lead anywhere. So
7 matches
Mail list logo
