From: "Lars Hjemli" <hjemli@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Suggestions for cgit (was: Re: suggestions for gitweb)
Date: Mon, 14 May 2007 10:50:04 +0200 [thread overview]
Message-ID: <8c5c35580705140150i85ef898h6ac0475ab12f8a03@mail.gmail.com> (raw)
In-Reply-To: <200705140931.32513.jnareb@gmail.com>
On 5/14/07, Jakub Narebski <jnareb@gmail.com> wrote:
> On Sun, 13 May 2007, Lars Hjemli <hjemli@gmail.com> wrote:
>
> > I've implemented number of files/lines changed in cgit's log view and
> > pushed it to http://hjemli.net/git/
> >
> > It does consume some cpu (especially on the linux-2.6 repo), but it's
> > not terribly bad (and the caching helps out). But I felt like changing
> > the number of commits per page to 50, so I added a knob for this in
> > the config file while at it.
> >
> > I'll try to get a proper diffstat on the commit page + file history
> > via tree view next (filesize has always been part of cgits tree view
> > btw).
>
> What I lack in cgit is using git diff and showing extended diff headers
> (and the ugly tight box around diff doesn't help either), and gitweb's
> 'commitdiff' view / git's git-show / git's git-format-patch.
Yes, this has been lacking. Last night I pushed initial support for
'commitdiff', but it doesn't show git's extended diff headers, nor is
there any plain/patch view (but the ugly tiny box is still there, I'm
lousy at web design :)
That said, extended headers/patch view should be trivial to support so
I'll look into it.
> I don't think displaying filesize slows cgit much (you need to find and
> read object header for that, as this information is not present in a
> tree object...
True, I do
type = sha1_object_info(sha1, &size)
per entry in tree view to get the size. It's fast.
> By the way, what do you think about http://git.or.cz/gitwiki/Gitweb
> page?
Nice, I hadn't noticed this page, maybe cgit should get one too? Well,
it probably should get some users first (are there anyone besides
myself?)
--
larsh
next prev parent reply other threads:[~2007-05-14 8:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 20:55 suggestions for gitweb Michael Niedermayer
2007-05-12 22:39 ` Junio C Hamano
2007-05-12 23:15 ` Aaron Gray
2007-05-13 0:41 ` Jakub Narebski
2007-05-13 0:54 ` Junio C Hamano
2007-05-13 11:50 ` Jakub Narebski
2007-05-13 16:52 ` Lars Hjemli
2007-05-14 7:31 ` Suggestions for cgit (was: Re: suggestions for gitweb) Jakub Narebski
2007-05-14 8:50 ` Lars Hjemli [this message]
2007-05-15 12:57 ` Lars Hjemli
2007-05-13 0:01 ` suggestions for gitweb Michael Niedermayer
2007-05-13 11:18 ` Jakub Narebski
2007-05-14 0:28 ` Junio C Hamano
2007-05-14 1:08 ` Petr Baudis
2007-05-14 2:00 ` Michael Niedermayer
2007-05-14 2:36 ` Petr Baudis
2007-05-14 8:53 ` Michael Niedermayer
2007-05-14 9:58 ` Petr Baudis
2007-05-14 16:49 ` Jakub Narebski
2007-05-14 17:37 ` Michael Niedermayer
2007-05-15 15:46 ` Jan Hudec
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=8c5c35580705140150i85ef898h6ac0475ab12f8a03@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).