From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH v2] Support Git over HTTP using git-http-backend
Date: Mon, 19 Jan 2015 17:58:15 +0100 [thread overview]
Message-ID: <CAHmME9o0P9mdQw2MJQaLEmczJUxx-xqKTzoDLBZjDoPxZnhC6g@mail.gmail.com> (raw)
In-Reply-To: <1419872165-23537-1-git-send-email-bluewind@xinu.at>
Do we really want to be enabling git-receive-pack? Seems like in its
present form, this could lead to some unexpected security results...
More generally, is this the right approach? Since we're linking against
git's sources anyway, couldn't any enhanced functionality be included
within cgit by calling into the right functions in the git source?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150119/6bcd3310/attachment.html>
next prev parent reply other threads:[~2015-01-19 16:58 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
2015-01-19 16:55 ` Jason
2015-01-19 17:08 ` cgit
2015-01-19 16:58 ` Jason [this message]
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=CAHmME9o0P9mdQw2MJQaLEmczJUxx-xqKTzoDLBZjDoPxZnhC6g@mail.gmail.com \
--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).