From: john at keeping.me.uk (John Keeping)
Subject: Bug: alternates not followed when enable-http-clone=1
Date: Mon, 28 Apr 2014 19:27:29 +0100 [thread overview]
Message-ID: <20140428182729.GA23935@serenity.lan> (raw)
In-Reply-To: <535E7F5F.9050401@kernel.org>
On Mon, Apr 28, 2014 at 12:18:39PM -0400, Konstantin Ryabitsev wrote:
> Someone tried to clone a cgit URL instead of the canonical clone URL for
> one of the projects and I thus discovered that cgit's http-clone support
> doesn't do the right thing with repositories that use alternates.
> Probably should be fixed.
Do you have absolute or relative paths in $GIT_DIR/info/alternates?
I can't see anything that CGit's HTTP implementation does differently
from git-http-backend, but gitrepository-layout(5) indicates that you
may need to create $GIT_DIR/info/http-alternates as well to provide the
correct paths to HTTP clients.
If you don't want CGit's HTTP clone, it might make more sense to just
turn it off in cgitrc ("enable-http-clone = 0").
next prev parent reply other threads:[~2014-04-28 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 16:18 mricon
2014-04-28 18:27 ` john [this message]
2014-04-30 16:32 ` mricon
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=20140428182729.GA23935@serenity.lan \
--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).