From: konstantin at linuxfoundation.org (Konstantin Ryabitsev)
Subject: repo.snapshot-prefix not working
Date: Tue, 17 Jul 2018 12:24:25 -0400 [thread overview]
Message-ID: <457baa6b-3bc5-0f7e-1b79-f8c9b05b9c54@linuxfoundation.org> (raw)
Hi, all:
Sorry that I didn't catch this earlier, but it looks like
repo.snapshot-prefix is not working, at least when I add it to the
repo-specific location in repo.git/cgitrc. I would guess this is because
the corresponding 'repo.snapshot-prefix' is missing from print_repo() in
cgit.c, so this setting is never added to the rc- file.
Best,
--
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180717/bc2bef0b/attachment.asc>
next reply other threads:[~2018-07-17 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:24 konstantin [this message]
2018-07-17 16:38 ` [PATCH] Record repo.snapshot-prefix in the per-repo config konstantin
2018-07-17 16:57 ` john
2018-07-17 17:12 ` 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=457baa6b-3bc5-0f7e-1b79-f8c9b05b9c54@linuxfoundation.org \
--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).