[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cgit
Subject:    Re: [PATCH v2] Support Git over HTTP using git-http-backend
From:       "Jason A. Donenfeld" <Jason () zx2c4 ! com>
Date:       2015-01-19 17:19:25
Message-ID: CAHmME9r_6OGp0pC_tr084S0Wx8Nj+8p86AU3FLv2cO+0g4_x3Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, Jan 19, 2015 at 6:13 PM, Lukas Fleischer <cgit@cryptocrack.de>
wrote:
>
> Please check my reply to v2 of Florian's patch, almost everything in
> http-backend.c is static which makes this difficult. We would need to
> convince Junio (the current Git maintainer) to make those functions
> public and probably send patches to Git. I would say it is okay to merge
> this implementation now and eventually switch to direct function calls.
>

On the contrary, I don't see any pressing need for this functionality now,
aside from an optimization of something that already exists. So I'd say
push ahead with actually implementing this properly - i.e. convincing Junio
& friends - and then go the correct route.

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan \
19, 2015 at 6:13 PM, Lukas Fleischer <span dir="ltr">&lt;<a \
href="mailto:cgit@cryptocrack.de" target="_blank">cgit@cryptocrack.de</a>&gt;</span> \
wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Please check my reply to v2 of Florian&#39;s patch, almost \
everything in<br> http-backend.c is static which makes this difficult. We would need \
to<br> convince Junio (the current Git maintainer) to make those functions<br>
public and probably send patches to Git. I would say it is okay to merge<br>
this implementation now and eventually switch to direct function \
calls.<br></blockquote><div><br></div><div>On the contrary, I don&#39;t see any \
pressing need for this functionality now, aside from an optimization of something \
that already exists. So I&#39;d say push ahead with actually implementing this \
properly - i.e. convincing Junio &amp; friends - and then go the correct route.  \
</div></div> </div></div>



_______________________________________________
CGit mailing list
CGit@lists.zx2c4.com
http://lists.zx2c4.com/mailman/listinfo/cgit


[prev in list] [next in list] [prev in thread] [next in thread]