From: bluewind at xinu.at (Florian Pritz)
Subject: [RFC] Relocate repos when using scan-path
Date: Sat, 18 May 2013 17:27:47 +0200 [thread overview]
Message-ID: <51979DF3.1030006@xinu.at> (raw)
In-Reply-To: <20130518151005.GC27005@serenity.lan>
On 18.05.2013 17:10, John Keeping wrote:
> On Mon, May 13, 2013 at 03:56:13PM +0200, Florian Pritz wrote:
>> Having now seen section-from-path now I think this feature is pretty
>> useful, but to fully utilize it I'd have to move around some repos for a
>> proper directory structure.
>>
>> Since I want to keep URLs working for existing clones I thought about
>> placing symlinks in the old location, but then cgit will display each
>> repo twice.
>>
>> Should there be an option to ignore symlinks, a (per repo) list of valid
>> paths for the index or something else to keep cgit's index list clean?
>
> I think what you want here is to return a "301 Moved Permanently"
> response on the old URLs. I considered adding this to CGit but I'm not
> sure we should add yet more configuration options when this can already
> be achieved with mod_rewrite or ngx_http_rewrite_module.
>
The point is that I want to keep already cloned repositories (as in "git
clone git://foo" via git-daemon) working and mod_rewrite won't help with
that even though it would probably work fine with the http clones.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20130518/32ae87c5/attachment.asc>
next prev parent reply other threads:[~2013-05-18 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:56 bluewind
2013-05-18 15:10 ` john
2013-05-18 15:25 ` Jason
2013-05-18 15:27 ` bluewind [this message]
2013-05-18 15:46 ` Jason
2013-05-18 16:06 ` john
2013-05-18 16:20 ` Jason
2013-05-18 16:48 ` john
2013-05-19 11:54 ` bluewind
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=51979DF3.1030006@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).