From: whydoubt at gmail.com (Jeffrey Smith)
Subject: [RFCv2 PATCH 1/7] ui-blame: create enable-blame config item
Date: Sat, 23 Sep 2017 22:12:26 -0500 [thread overview]
Message-ID: <CAPX7N=5raVzxt+HNp=5w61vXVPMp+zPZiC5ORz6z77LkHJAJtQ@mail.gmail.com> (raw)
In-Reply-To: <20170923154656.GA2548@john.keeping.me.uk>
I don't have a strong opinion one way or the other.
I suppose setting it to false would avoid springing the potential
added resource use on people, as blame can be a relatively
expensive operation.
On Sat, Sep 23, 2017 at 10:46 AM, John Keeping <john at keeping.me.uk> wrote:
> On Fri, Sep 22, 2017 at 10:38:42PM -0500, Jeff Smith wrote:
>> Signed-off-by: Jeff Smith <whydoubt at gmail.com>
>> ---
>> cgit.c | 3 +++
>> cgit.h | 1 +
>> cgitrc.5.txt | 5 +++++
>> 3 files changed, 9 insertions(+)
>>
>> diff --git a/cgit.c b/cgit.c
>> index 1dae4b8..c03f69c 100644
>> --- a/cgit.c
>> +++ b/cgit.c
>> @@ -183,6 +183,8 @@ static void config_cb(const char *name, const char *value)
>> ctx.cfg.enable_tree_linenumbers = atoi(value);
>> else if (!strcmp(name, "enable-git-config"))
>> ctx.cfg.enable_git_config = atoi(value);
>> + else if (!strcmp(name, "enable-blame"))
>> + ctx.cfg.enable_blame = atoi(value);
>> else if (!strcmp(name, "max-stats"))
>> ctx.cfg.max_stats = cgit_find_stats_period(value, NULL);
>> else if (!strcmp(name, "cache-size"))
>> @@ -373,6 +375,7 @@ static void prepare_context(void)
>> ctx.cfg.enable_index_owner = 1;
>> ctx.cfg.enable_tree_linenumbers = 1;
>> ctx.cfg.enable_git_config = 0;
>> + ctx.cfg.enable_blame = 1;
>
> Should this default to false? Either way, I think the commit message
> should have some discussion of what the default is any why it has been
> chosen.
>
>> ctx.cfg.max_repo_count = 50;
>> ctx.cfg.max_commit_count = 50;
>> ctx.cfg.max_lock_attempts = 5;
>> diff --git a/cgit.h b/cgit.h
>> index fbc6c6a..a48e622 100644
>> --- a/cgit.h
>> +++ b/cgit.h
>> @@ -236,6 +236,7 @@ struct cgit_config {
>> int enable_html_serving;
>> int enable_tree_linenumbers;
>> int enable_git_config;
>> + int enable_blame;
>> int local_time;
>> int max_atom_items;
>> int max_repo_count;
>> diff --git a/cgitrc.5.txt b/cgitrc.5.txt
>> index 9fcf445..b236bf2 100644
>> --- a/cgitrc.5.txt
>> +++ b/cgitrc.5.txt
>> @@ -211,6 +211,11 @@ enable-git-config::
>> with "cgit." will be mapped to the corresponding "repo." key in cgit.
>> Default value: "0". See also: scan-path, section-from-path.
>>
>> +enable-blame::
>> + Flag which, when set to "1", will allow cgit to provide a "blame" page
>> + for files, and will make it generate links to that page in appropriate
>> + places. Default value: "1".
>> +
>
> Although the handful of enable-* options above this are not well sorted,
> most of this file is, so this should move to above enable-commit-graph.
>
>> favicon::
>> Url used as link to a shortcut icon for cgit. It is suggested to use
>> the value "/favicon.ico" since certain browsers will ignore other
next prev parent reply other threads:[~2017-09-24 3:12 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 2:18 [RFC PATCH 0/4] Add ui-blame whydoubt
2017-06-08 2:18 ` [RFC PATCH 1/4] git: update to v2.14 whydoubt
2017-07-22 11:25 ` john
2017-06-08 2:18 ` [RFC PATCH 2/4] ui-blame: create placeholder and links whydoubt
2017-07-22 11:31 ` john
2017-06-08 2:18 ` [RFC PATCH 3/4] ui-blame: create needed html_ntxt_noellipsis function whydoubt
2017-07-22 11:36 ` john
2017-06-08 2:18 ` [RFC PATCH 4/4] ui-blame: fill in the contents whydoubt
2017-07-05 8:32 ` list
2017-07-22 11:47 ` john
2017-06-08 9:00 ` [RFC PATCH 0/4] Add ui-blame list
2017-07-22 12:02 ` john
2017-08-05 0:23 ` dlcampbell
2017-08-05 0:57 ` whydoubt
2017-08-24 18:14 ` list
2017-08-31 13:05 ` whydoubt
2017-09-23 3:38 ` [RFCv2 PATCH 0/7] " whydoubt
2017-09-23 3:38 ` [RFCv2 PATCH 1/7] ui-blame: create enable-blame config item whydoubt
2017-09-23 15:46 ` john
2017-09-24 3:12 ` whydoubt [this message]
2017-09-23 3:38 ` [RFCv2 PATCH 2/7] ui-blame: create framework whydoubt
2017-09-23 15:47 ` john
2017-09-24 3:24 ` whydoubt
2017-09-23 3:38 ` [RFCv2 PATCH 3/7] ui-blame: create links whydoubt
2017-09-23 15:47 ` john
2017-09-24 20:25 ` whydoubt
2017-09-23 3:38 ` [RFCv2 PATCH 4/7] ui-blame: html_ntxt with no ellipsis whydoubt
2017-09-23 15:47 ` john
2017-09-23 3:38 ` [RFCv2 PATCH 5/7] ui-blame: pull blame info from libgit whydoubt
2017-09-23 15:47 ` john
2017-09-24 19:06 ` whydoubt
2017-09-24 20:09 ` whydoubt
2017-09-24 20:52 ` john
2017-09-23 3:38 ` [RFCv2 PATCH 6/7] ui-blame: begin building whydoubt
2017-09-23 3:38 ` [RFCv2 PATCH 7/7] ui-blame: generate blame page when requested whydoubt
2017-09-23 15:53 ` [RFCv2 PATCH 0/7] Add ui-blame john
2017-09-24 3:05 ` whydoubt
2017-09-27 22:43 ` [PATCH 0/5] " whydoubt
2017-09-27 22:43 ` [PATCH 1/5] html: html_ntxt with no ellipsis whydoubt
2017-09-30 11:55 ` john
2017-09-27 22:43 ` [PATCH 2/5] ui-tree: move set_title_from_path to ui-shared whydoubt
2017-09-30 11:56 ` john
2017-09-27 22:43 ` [PATCH 3/5] ui-shared: make a char* parameter const whydoubt
2017-09-30 12:00 ` john
2017-09-27 22:43 ` [PATCH 4/5] ui-blame: add blame UI whydoubt
2017-09-30 12:07 ` john
2017-09-27 22:43 ` [PATCH 5/5] ui-tree: link to blame UI if enabled whydoubt
2017-09-30 12:08 ` john
2017-09-30 12:10 ` [PATCH 0/5] Add ui-blame john
2017-10-02 1:17 ` Jason
2017-10-02 5:34 ` list
2017-10-02 22:35 ` whydoubt
2017-10-02 23:29 ` list
2017-10-03 18:22 ` john
2017-10-03 18:23 ` Jason
2017-10-03 18:36 ` Jason
2017-10-03 19:06 ` whydoubt
2017-10-02 4:39 ` [PATCHv2 " whydoubt
2017-10-02 4:39 ` [PATCHv2 1/5] html: html_ntxt with no ellipsis whydoubt
2017-10-02 4:39 ` [PATCHv2 2/5] ui-tree: move set_title_from_path to ui-shared whydoubt
2017-10-02 4:39 ` [PATCHv2 3/5] ui-shared: make a char* parameter const whydoubt
2017-10-02 4:39 ` [PATCHv2 4/5] ui-blame: add blame UI whydoubt
2017-10-02 4:39 ` [PATCHv2 5/5] ui-tree: link to blame UI if enabled whydoubt
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='CAPX7N=5raVzxt+HNp=5w61vXVPMp+zPZiC5ORz6z77LkHJAJtQ@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).