List for cgit developers and users
 help / color / mirror / Atom feed
From: mohun106 at gmail.com (Radha Mohan)
Subject: reduce number of tags in log/summary view
Date: Wed, 19 Oct 2016 13:55:40 -0700	[thread overview]
Message-ID: <CAC8NTUVXT1xFr=_uH1k2OHXk=ycpH0-_jkBrBLbvjoVP9Ddf7A@mail.gmail.com> (raw)
In-Reply-To: <20161009113551.GO1997@john.keeping.me.uk>

On Sun, Oct 9, 2016 at 4:35 AM, John Keeping <john at keeping.me.uk> wrote:
> On Wed, Oct 05, 2016 at 10:10:42PM -0700, Radha Mohan wrote:
>> I am looking for an option (if any) in cgitrc that can reduce the
>> number for tags of branch shown in log view or summary view.
>>
>> I have a situation where a branch is tagged by our automatic build
>> systems. If on some branch the commit doesn't move ahead the web view
>> makes it clumsy. We have to scroll horizontally to see the full info
>> as all the tags occupy the space in a single line.
>>
>> If an option exists that can control the number of tags in this kind
>> of situation that would be helpful.
>
> The only option that affects this at the moment is the
> enable-remote-branches setting, which defaults to false.  It doesn't
> sound like you have remote branches, so I don't think that will help.
>
> What does your ideal end result look like?  How should we choose which
> refs to drop, and where can users find the dropped refs?

My situation is exactly similar to what Konstantin pointed. Pasting his link
https://source.codeaurora.org/quic/la/platform/external/chromium_org/log/?h=LA.AF.1.1.1

If you hover over the first log, there are about 8 tags and 5 branch
points at the HEAD. Without the css trick that Konstantin is using the
page will be long horizontally which is clumsy.

So if we can do this:
1) Give an option to limit the entries (tag and branch name combined)
2) Add a tooltip kind of icon (like ">>") beside each tags and
branches separately when the limit specified in 1 above is reached.
Put the extra/old ones under this, just like in the CSS trick.

Maybe there are other options to do this. Mine is just a idea to
reduce clumsiness of the web view. People shouldn't turn away from
cgit due to this :)

>
> My only thought at the moment is to support switching on/off branch and
> tag names in addition to the existing support for remote branches, or to
> allow filtering by pattern or regex.


      reply	other threads:[~2016-10-19 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  5:10 mohun106
2016-10-09 11:35 ` john
2016-10-19 20:55   ` mohun106 [this message]

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='CAC8NTUVXT1xFr=_uH1k2OHXk=ycpH0-_jkBrBLbvjoVP9Ddf7A@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).