From: bluewind at xinu.at (Florian Pritz)
Subject: [PATCH v2] Support Git over HTTP using git-http-backend
Date: Fri, 16 Jan 2015 00:57:26 +0100 [thread overview]
Message-ID: <54B853E6.3050309@xinu.at> (raw)
In-Reply-To: <20141229171611.32032.28075@typhoon.lan>
On 29.12.2014 18:16, Lukas Fleischer wrote:
> On Mon, 29 Dec 2014 at 17:56:05, Florian Pritz wrote:
>> This saves users from the hassle of setting up git-http-backend when
>> they already run cgit.
>>
>> References: man git-http-backend
Since this has not yet been merged and it currently conflicts with
master: Is there any interest in the patch? If yes, I'd be happy to
resolve the conflict.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150116/669ef9dd/attachment.asc>
next prev parent reply other threads:[~2015-01-15 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 16:13 [PATCH] " bluewind
2014-12-29 16:56 ` [PATCH v2] " bluewind
2014-12-29 17:16 ` cgit
2015-01-15 23:57 ` bluewind [this message]
2015-01-19 16:55 ` Jason
2015-01-19 17:08 ` cgit
2015-01-19 16:58 ` Jason
2015-01-19 17:13 ` cgit
2015-01-19 17:19 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B853E6.3050309@xinu.at \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).