From: john at keeping.me.uk (John Keeping)
Subject: Adding short commit id to repo Log tab
Date: Sat, 16 Jun 2018 17:21:11 +0100 [thread overview]
Message-ID: <20180616162111.GC1922@john.keeping.me.uk> (raw)
In-Reply-To: <CALR6X0-iENNxSb593ADmdpe+cwxwbj6VVSA1cOf=2A__U5eCwg@mail.gmail.com>
Sorry for the delay responding.
On Wed, Apr 11, 2018 at 12:00:28PM +0300, Vlad wrote:
> I think adding short (7 chars) commit id to repository Log tab output
> might be more useful than file or line count..
>
> I have examined the code, it it not easy to add an extra column
> to the output.
>
> Would you suggest ways how to implement this?
I'm not sure I agree that this is useful, but personally I wouldn't be
opposed to adding this if the code is simple.
I don't think it's hard to do, you just need to add a new <th> element
in cgit_print_log() and then write the <tr> element in print_commit(),
making sure that columns is also adjusted. All of the code should be in
ui-log.c unless you add a config switch to enable this feature..
next prev parent reply other threads:[~2018-06-16 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 9:00 thevlad
2018-06-16 16:21 ` john [this message]
2018-06-17 21:00 ` thevlad
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=20180616162111.GC1922@john.keeping.me.uk \
--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).