git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Daniel Serpell <daniel.serpell@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: More gitweb queries..
Date: Sun, 29 May 2005 08:43:48 +1000	[thread overview]
Message-ID: <1117320229.5228.18.camel@gaston> (raw)
In-Reply-To: <20050528084255.GA32614@vrfy.org>

On Sat, 2005-05-28 at 10:42 +0200, Kay Sievers wrote:

> You know how that stuff works? :) It is a very nice idea for
> small stuff, but it uses a <div> for every pixel/line you draw and
> places this in the background and I expect it to kill your browser if
> you try to draw things like gitk does.
> 
> > Alternatively, you could use a fixed set of little images, a bar "|", a
> > dot "o" and branches like "Y", "7" and "\". Obviously, octopus-merges
> > are very difficult to draw using only those.
> 
> Did you look at gitk? With a all the crossing and long lines, you definitely
> need to draw the lines with colors. Otherwise you will see _nothing_, but
> random characters. :)
> 
> > BTW, I tried searching on gitweb, and I think that found a problem, see:
> > http://ehlo.org/~kay/gitweb.cgi?p=git/git.git;a=search;s=check
> > At the bottom of the page, highlighting of the search term stops and the
> > commits are all the same color.
> 
> Well, you see a list of files which contain the text, not the text
> itself. I can print the filename in red. :)

Best may be to have the server generate a picture ... ?

Ben.



  reply	other threads:[~2005-05-28 22:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 19:24 More gitweb queries Linus Torvalds
2005-05-27 19:29 ` Thomas Glanzmann
2005-05-27 19:52   ` Junio C Hamano
2005-05-27 19:55     ` Thomas Glanzmann
2005-05-27 20:13       ` Junio C Hamano
2005-05-27 20:32         ` Thomas Glanzmann
2005-05-27 20:40           ` Junio C Hamano
2005-05-27 22:00             ` Linus Torvalds
2005-05-27 22:04               ` Thomas Glanzmann
2005-05-28  2:26               ` Junio C Hamano
2005-05-29 23:02           ` Thomas Glanzmann
2005-05-29 23:10             ` Thomas Glanzmann
2005-05-29 23:16               ` Thomas Glanzmann
2005-05-29 23:46                 ` Thomas Glanzmann
2005-05-29 23:56                   ` Thomas Glanzmann
2005-05-30  0:50                     ` Junio C Hamano
2005-05-30  0:57                       ` Junio C Hamano
2005-05-30  1:33                         ` Thomas Glanzmann
2005-05-30  1:30                       ` Thomas Glanzmann
2005-05-30  7:57                         ` Junio C Hamano
2005-05-30  8:36                           ` Thomas Glanzmann
2005-05-30  9:21                             ` Thomas Glanzmann
2005-05-30 10:20                               ` Junio C Hamano
2005-05-30 12:11                                 ` Thomas Glanzmann
2005-05-30 17:54                                   ` Junio C Hamano
2005-05-27 20:17       ` Linus Torvalds
2005-05-27 19:54   ` Junio C Hamano
2005-05-27 19:58     ` Thomas Glanzmann
2005-05-27 20:03   ` Linus Torvalds
2005-05-27 20:24     ` Junio C Hamano
2005-05-27 19:31 ` Thomas Glanzmann
2005-05-27 19:32 ` Junio C Hamano
2005-05-27 19:48   ` Linus Torvalds
2005-05-27 23:12 ` Benjamin Herrenschmidt
2005-05-27 23:59 ` Kay Sievers
2005-05-28  1:03   ` Daniel Serpell
2005-05-28  2:51     ` David Lang
2005-05-28 10:56       ` Kay Sievers
2005-05-28  8:42     ` Kay Sievers
2005-05-28 22:43       ` Benjamin Herrenschmidt [this message]
2005-05-30 23:03 ` Paul Mackerras
2005-05-31  2:27   ` Jeff Epler

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=1117320229.5228.18.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=daniel.serpell@gmail.com \
    --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).