Re: [PATCH] RFC/Add documentation for version protocol 2

2015-04-22 Thread Stefan Beller
On Wed, Apr 22, 2015 at 4:30 PM, Junio C Hamano wrote: > Stefan Beller writes: > +action = "noop" / "ls-remote" / "fetch" / "push" / "fetch-shallow" >> ... >>> If we are going in this "in-protocol message switches the service" >>> route, we should also support "archive" as on

Re: [PATCH] RFC/Add documentation for version protocol 2

2015-04-22 Thread Junio C Hamano
Stefan Beller writes: >>> +action = "noop" / "ls-remote" / "fetch" / "push" / >>> "fetch-shallow" > ... >> If we are going in this "in-protocol message switches the service" >> route, we should also support "archive" as one of the actions, no? >> Yes, I know you named the document "pac

Re: [PATCH] RFC/Add documentation for version protocol 2

2015-04-22 Thread Stefan Beller
On Wed, Apr 22, 2015 at 12:19 PM, Junio C Hamano wrote: > Stefan Beller writes: > >> This adds the design document for protocol version 2. >> It's better to rewrite the design document instead of trying to >> squash it into the existing pack-protocol.txt and then differentiating >> between versio

Re: [PATCH] RFC/Add documentation for version protocol 2

2015-04-22 Thread Junio C Hamano
Stefan Beller writes: > This adds the design document for protocol version 2. > It's better to rewrite the design document instead of trying to > squash it into the existing pack-protocol.txt and then differentiating > between version 1 and 2 all the time. Just a handful of random thoughts, with

[PATCH] RFC/Add documentation for version protocol 2

2015-04-21 Thread Stefan Beller
This adds the design document for protocol version 2. It's better to rewrite the design document instead of trying to squash it into the existing pack-protocol.txt and then differentiating between version 1 and 2 all the time. Signed-off-by: Stefan Beller --- As we discussed at Git Merge in P