From: Michael Niedermayer <michaelni@gmx.at>
To: git@vger.kernel.org
Subject: suggestions for gitweb
Date: Sat, 12 May 2007 22:55:30 +0200 [thread overview]
Message-ID: <20070512205529.GS14859@MichaelsNB> (raw)
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
Hi
As we are switching from svn to git, we also have to switch from viewvc to
gitweb (or similar) and so ive thought id submit a short list of things
ive noticed in gitweb which i belive could be improved ...
* gitweb uses many terms which are new to a non git user, and while
devlopers who work on ffmpeg will very likely very quickly have
figured out the meaning of all of them. i think simple users who just
want to browse the ffmpeg code will have their problems, so i belive
a small help text linked to from all pages which contains a short
definition of all the git(web) specific terms would be very helpfull
something like
blob - file at a specific revission/date
tree - directory at a specific revission/date
(short) log - project wide commit log
history - short log equivalent for a file or directory
...
* The color of adjacent blame "hunks" is so similar that its
indistinguishable on my notebook TFT when iam looking at it from slightly
above
* The blame page shows the SHA1 for each hunk and IMHO thats the last thing
i would want to see first, id be much more interrested in by whom and
when a given change was done, iam wondering in which case the SHA1 would
be usefull? copy-paste onto your command line git tools but then why
use gitweb at all, 'git blame' would make more sense IMHO and a simple
click would reveal the sha1 with more info anyway ...
* i either cant find the long history for a file or there is none ("history"
is like "short log" and "log" is not file specific) a "long history" link
in addition to "history" would be nice
* on the history page there are "blob", "commitdiff" and "diff to current"
the obvious missing one is "diff to previous" which would be the diff to
the previous blob of this file
* the history/log pages could contain some statistics for the commits like
the number of files changed and lines added/removed
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-05-12 20:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 20:55 Michael Niedermayer [this message]
2007-05-12 22:39 ` suggestions for gitweb 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
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=20070512205529.GS14859@MichaelsNB \
--to=michaelni@gmx.at \
--cc=git@vger.kernel.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).