From: Chris Shoemaker <c.shoemaker@cox.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH gitweb] Visually indicating patch size with horizontal bars
Date: Thu, 27 Oct 2005 22:38:33 -0400 [thread overview]
Message-ID: <20051028023833.GA19939@pe.Belkin> (raw)
In-Reply-To: <20051028015642.GA31822@vrfy.org>
On Fri, Oct 28, 2005 at 03:56:42AM +0200, Kay Sievers wrote:
> On Thu, Oct 27, 2005 at 04:39:45PM -0400, Chris Shoemaker wrote:
> >
> > I really like gitweb (thanks Kay!), but I thought it would be nice to
> > have a visual indication of patch size. I found this helpful when
> > scanning though the shortlogs.
>
> This looks nice, but if the patch size tells you something important,
> your commit subjects are probably too short or wrong. :)
Yeah, some people write lousy commit subjects. But me? Nooo,
/never/. :)
> You may try to use CSS instead of an embedded picture to draw the bar,
> just like the RSS logo in the footer, which is simple CSS rendered in the
> browser.
I'll look into that, but the cost wasn't in the image; it was in the
width calculation.
Here's a side-by-side comparison. Open two browser tabs and flip between them:
http://www.codesifter.com/cgi-bin/gitweb-difftreeP.cgi?p=git.git;a=shortlog
http://www.codesifter.com/cgi-bin/gitweb-difftreeNames.cgi?p=git.git;a=shortlog
I've used a project you all are familar with, and that has more than
two files. The first page uses 'git-diff-tree -p $hash|wc -l'. The
second page uses 'git-diff-tree -r --name-only|wc -l'. (Oh and I have
a merge indicator now.)
How do they compare for showing damage-potential? I think they both
do a reasonable job. I think the full patch diff is a bit better, but
it does cost.
-chris
next prev parent reply other threads:[~2005-10-28 2:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 20:39 [PATCH gitweb] Visually indicating patch size with horizontal bars Chris Shoemaker
2005-10-27 22:02 ` Junio C Hamano
2005-10-27 23:48 ` Chris Shoemaker
2005-10-28 0:12 ` Linus Torvalds
2005-10-28 0:50 ` Chris Shoemaker
2005-10-28 1:08 ` Martin Langhoff
2005-10-28 1:13 ` H. Peter Anvin
2005-10-28 8:29 ` Andreas Ericsson
2005-10-28 9:31 ` Junio C Hamano
2005-10-28 1:16 ` Martin Langhoff
2005-10-28 2:38 ` Linus Torvalds
2005-10-28 3:52 ` Junio C Hamano
2005-10-28 16:02 ` Linus Torvalds
2005-10-28 1:56 ` Kay Sievers
2005-10-28 2:38 ` Chris Shoemaker [this message]
2005-11-01 23:30 ` Petr Baudis
2005-11-01 23:33 ` Martin Langhoff
2005-11-01 23:43 ` Petr Baudis
2005-11-02 8:08 ` Andreas Ericsson
2005-11-02 10:37 ` Johannes Schindelin
2005-11-02 12:19 ` Andreas Ericsson
2005-11-02 12:43 ` Johannes Schindelin
2005-11-02 0:12 ` Chris Shoemaker
2005-11-02 0:26 ` Kay Sievers
2005-12-05 0:04 ` Petr Baudis
2005-12-05 1:03 ` Chris Shoemaker
2005-10-28 9:16 ` Josef Weidendorfer
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=20051028023833.GA19939@pe.Belkin \
--to=c.shoemaker@cox.net \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
/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).