git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Shoemaker <c.shoemaker@cox.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH gitweb] Visually indicating patch size with horizontal bars
Date: Thu, 27 Oct 2005 19:48:13 -0400	[thread overview]
Message-ID: <20051027234813.GA512@pe.Belkin> (raw)
In-Reply-To: <7vfyqm1uvx.fsf@assigned-by-dhcp.cox.net>

On Thu, Oct 27, 2005 at 03:02:10PM -0700, Junio C Hamano wrote:
> Chris Shoemaker <c.shoemaker@cox.net> writes:
> 
> > If anyone thinks this is a good feature, then please tell me an
> > efficient way to get some heuristic of the patch size.
> >
> > Right now, I'm using: 
> >
> > GIT_DIFF_OPTS='-U 0' $gitbin/git-diff-tree -p $hash | wc -l
> >
> > which is pretty slow.  Any suggestions?
> 
> * do we really want to know the number of lines?  sometimes the
>   number of pahts that are affected is more useful than number
>   of lines when assessing the damage, which can be done with
>   'git-diff-tree --name-only'.

That only shows the top-level names, so when 100s of files changes in
a subdir it looks just like one entry.  It's ok when there's no
subdirs, but it just doesn't work when 95% of the code is under,
e.g. src/.

> 
> * cache the result -- they never change.

True.  Maybe gitk and gitweb can share a cache containing the tree
diffs.  Or maybe git-core can cache tree diffs?

> 
> An interesting question is what to do with merges, but probably
> we can just ignore it for now.

It's trivial to, e.g. use a different image for merges, maybe based on
# of parents?

But, in general, is there interest in a visual indicator of commit
size and/or type in gitweb?

-chris

  reply	other threads:[~2005-10-27 23:48 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 [this message]
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
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=20051027234813.GA512@pe.Belkin \
    --to=c.shoemaker@cox.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).