git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Luben Tuikov <ltuikov@yahoo.com>, Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: Show trailing slash when listing tree entry in tree listing
Date: Mon, 9 Oct 2006 22:55:51 +0200	[thread overview]
Message-ID: <20061009205551.GO20017@pasky.or.cz> (raw)
In-Reply-To: <20061007191246.GF20017@pasky.or.cz>

> Dear diary, on Sat, Oct 07, 2006 at 09:06:25PM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
> > By the way, I miss somewhat the "redundant" tree/blob links in tree
> > view...
> 
> I didn't want to post about it but I share the feeling - I have to keep
> thinking consciously about clicking on the file name instead of on the
> view name - and the situation is worse for regular files, since it is
> not really apparent that the filenames are clickablea. My mind knows
> that I'm supposed to click on them (not users' mind!), but the eyes and
> hands are still clueless.

I was looking into accesslogs of repo.or.cz for something and noticed
that I see unusually large number of blame requests. That of course
attracted my curiosity and I came to conclusion that what I'm seeing is
not just my personal whim but we have serious usability problem here.

I'm unfortunately not sure when the update of repo.or.cz gitweb which
dropped the blob/tree links happenned, so the following _is_ somewhat
dubious, but I think it's quite telling anyway.

I have three samples (logfiles) available: #2 almost certainly when the
blob link was still there, #1 covering the switch and some time before
and after, and #0 certainly when the blob link was not there anymore,
but unfortunately spanning only one or two days.

This is the count of actions invoked from the tree, commit and
commitdiff view (using the referer information):

    blame  blob   total requests containing 'a='
#2  1      18     264
#1  31     23     399
#0  4      6      50

The disparation between #2 and #1,#0 is quite apparent. If we want more
exact results, I will let #0 accumulate data for a week and then revert
the removal of the links and start another sample.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

  parent reply	other threads:[~2006-10-09 20:55 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 19:22 [PATCH] gitweb: Do not print "log" and "shortlog" redundantly in commit view Luben Tuikov
2006-10-06  7:44 ` Jakub Narebski
2006-10-06 16:35   ` Petr Baudis
2006-10-06 22:16   ` Luben Tuikov
2006-10-07 13:24     ` Petr Baudis
2006-10-07 14:05       ` Jakub Narebski
2006-10-07 14:17         ` Petr Baudis
2006-10-07 14:10       ` [PATCH 1/2] gitweb: Show snapshot links for tree entries in tree listing Petr Baudis
2006-10-07 18:37         ` Luben Tuikov
2006-10-07 18:41           ` Petr Baudis
2006-10-07 18:52             ` Luben Tuikov
2006-10-07 19:15               ` Petr Baudis
2006-10-07 22:31                 ` Junio C Hamano
2006-10-08  1:04                 ` Luben Tuikov
2006-10-07 14:10       ` [PATCH 2/2] gitweb: Show trailing slash when listing tree entry " Petr Baudis
2006-10-07 18:44         ` Luben Tuikov
2006-10-07 19:06           ` Jakub Narebski
2006-10-07 19:12             ` Petr Baudis
2006-10-07 20:38               ` Jakub Narebski
2006-10-07 21:15                 ` Petr Baudis
2006-10-07 21:27                   ` Jakub Narebski
2006-10-09 20:55               ` Petr Baudis [this message]
2006-10-09 22:52                 ` Junio C Hamano
2006-10-10  5:10                   ` Junio C Hamano
2006-10-10  5:38                     ` Luben Tuikov
2006-10-10  5:46                       ` Junio C Hamano
2006-10-10  6:34                         ` Luben Tuikov
2006-10-10  5:46                       ` Jeff King
2006-10-10  6:41                         ` Luben Tuikov
2006-10-10  6:58                           ` Jeff King
2006-10-10  9:15                       ` Jakub Narebski
2006-10-10 19:19                         ` Luben Tuikov
2006-10-10 19:57                           ` Junio C Hamano
2006-10-10 20:31                             ` Jakub Narebski
2006-10-10 21:02                               ` Luben Tuikov
2006-10-10 21:13                                 ` Jakub Narebski
2006-10-10 22:18                                   ` Luben Tuikov
2006-10-10 20:52                             ` Luben Tuikov
2006-10-10 21:00                               ` Jakub Narebski
2006-10-10 22:14                                 ` Luben Tuikov
2006-10-10 22:40                                   ` Jakub Narebski
2006-10-10 20:29                           ` Jakub Narebski
2006-10-11 15:35                           ` Andreas Ericsson
2006-10-10  6:21                 ` Luben Tuikov
2006-10-10  7:05                   ` Jeff King
2006-10-10  8:07                     ` Andreas Ericsson
2006-10-10 13:14                       ` Josef Weidendorfer
2006-10-10 18:23                         ` Luben Tuikov
2006-10-10 18:52                           ` Josef Weidendorfer
2006-10-10 18:50                         ` Luben Tuikov
2006-10-10  8:28                     ` Junio C Hamano
2006-10-07 21:31           ` A Large Angry SCM
2006-10-07 22:34           ` Junio C Hamano
2006-10-08  1:16             ` Luben Tuikov

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=20061009205551.GO20017@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=ltuikov@yahoo.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).