From: John Keeping <john@keeping.me.uk>
To: Kian Kasad <kian@kasad.com>
Cc: cgit@lists.zx2c4.com
Subject: Re: User-configurable log graph option
Date: Fri, 19 Feb 2021 12:22:03 +0000 [thread overview]
Message-ID: <YC+ta4Iwev/Wuhii@john.keeping.me.uk> (raw)
In-Reply-To: <20210218223126.yrgfjni73fi4rvw4@frisbee>
On Thu, Feb 18, 2021 at 02:31:26PM -0800, Kian Kasad wrote:
> I'm using cgit on my website and I'm wondering if it's possible to allow
> the user (i.e. the person visiting the site) to choose whether or not
> the commit graph is displayed on the log page.
>
> If this isn't currently possible, what do you think about adding such
> functionality? Maybe something like how the diff page lets the user
> choose between a "unified diff" and "ssdiff".
This sounds like a great new feature!
I think we still want to allow the administrator to turn the feature
on/off but if it is permitted, then it makes sense to allow the end user
to choose whether or not they want it enabled.
Patches welcome :-)
next prev parent reply other threads:[~2021-02-19 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 22:31 Kian Kasad
2021-02-19 12:22 ` John Keeping [this message]
2021-12-30 21:08 ` Kian Kasad
2022-08-05 4:59 ` [PATCH 0/6] Option for separate 'log' and 'graph' pages Kian Kasad
2022-08-05 4:59 ` [PATCH 1/6] Implement parsing of new enable-commit-graph option Kian Kasad
2022-08-05 4:59 ` [PATCH 2/6] Add graph page Kian Kasad
2022-08-05 4:59 ` [PATCH 3/6] Don't display commit age on " Kian Kasad
2022-08-05 4:59 ` [PATCH 4/6] Don't display graph page if enable-commit-graph is not set to "separate" Kian Kasad
2022-08-05 4:59 ` [PATCH 5/6] Add graph page tab if enable-commit-graph is " Kian Kasad
2022-08-05 4:59 ` [PATCH 6/6] Document new enable-commit-graph option Kian Kasad
2023-01-05 23:14 ` Follow-up: User-configurable log graph option Kian Kasad
2023-07-01 6:28 ` Daniel Campbell
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=YC+ta4Iwev/Wuhii@john.keeping.me.uk \
--to=john@keeping.me.uk \
--cc=cgit@lists.zx2c4.com \
--cc=kian@kasad.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).