Re: [PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-05-04 Thread Junio C Hamano
David Turner writes: > On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: >> In upload-pack-2 we send each capability in its own packet buffer. >> The construction of upload-pack-2 is a bit unfortunate as I would >> like >> it to not be depending on a symlink

Re: [PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-05-02 Thread Duy Nguyen
On Tue, May 3, 2016 at 1:56 AM, David Turner wrote: > On Mon, 2016-05-02 at 10:51 -0700, Stefan Beller wrote: >> On Mon, May 2, 2016 at 10:43 AM, David Turner < >> dtur...@twopensource.com> wrote: >> > On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: >> > > In

Re: [PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-05-02 Thread David Turner
On Mon, 2016-05-02 at 10:51 -0700, Stefan Beller wrote: > On Mon, May 2, 2016 at 10:43 AM, David Turner < > dtur...@twopensource.com> wrote: > > On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: > > > In upload-pack-2 we send each capability in its own packet > > > buffer. > > > The

Re: [PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-05-02 Thread Stefan Beller
On Mon, May 2, 2016 at 10:43 AM, David Turner wrote: > On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: >> In upload-pack-2 we send each capability in its own packet buffer. >> The construction of upload-pack-2 is a bit unfortunate as I would >> like >> it to not

Re: [PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-05-02 Thread David Turner
On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: > In upload-pack-2 we send each capability in its own packet buffer. > The construction of upload-pack-2 is a bit unfortunate as I would > like > it to not be depending on a symlink linking to upload-pack.c, but I > did > not find another

[PATCH 03/14] upload-pack-2: Implement the version 2 of upload-pack

2016-04-29 Thread Stefan Beller
In upload-pack-2 we send each capability in its own packet buffer. The construction of upload-pack-2 is a bit unfortunate as I would like it to not be depending on a symlink linking to upload-pack.c, but I did not find another easy way to do it. I would like it to generate upload-pack-2.o from