From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH/RFC 0/4] gitweb: ViewVC-like "tree_blame" view
Date: Thu, 31 Aug 2006 00:43:12 +0200 [thread overview]
Message-ID: <200608310043.12606.jnareb@gmail.com> (raw)
In response to Thomas Glanzmann (or rather a friend of his) request,
here is series of patches which adds to tree view information about
when last time and by whom was given file or directory touched. As git
records "snapshot history" and commits are whole tree, and not have per
file history, it means that one wants to know last commit counting from
the top which has the same version of file or the same tree. This is
something similar to blame (aka. annotate) for file, hence naming such
view "tree_blame".
Current implementation is done inefficiently directly in gitweb, and
serves rather as a proof of concept than as a serious implementation to
use.
This series of patches is based on 'next' (v1.4.2-g39ee2f6) equivalent,
but with the commit 25691fbe6d02135d55dfc3a5180e29890dce1521
gitweb: Use --git-dir parameter instead of setting $ENV{'GIT_DIR'}
reverted, as it needs git version post v1.4.2-rc2, while I use git
version 1.4.1.1, as there are no i386 RPMS for 1.4.2 yet.
ViewCVS/ViewVC prints the last touch of a a file in a directory and you
can tell it to sort after the date criteria:
http://faumachine.informatik.uni-erlangen.de/cgi-bin/viewcvs.cgi/mutt/?sortby=date#dirlist
--
Jakub Narebski
ShadeHawk on #git
Poland
next reply other threads:[~2006-08-30 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:43 Jakub Narebski [this message]
2006-08-30 23:08 ` [PATCH/RFC 0/4] gitweb: ViewVC-like "tree_blame" view Jakub Narebski
2006-08-31 0:00 ` Junio C Hamano
2006-08-31 0:18 ` Jakub Narebski
2006-08-31 0:47 ` Josef Weidendorfer
2006-08-31 1:05 ` Jakub Narebski
2006-08-31 9:22 ` Jakub Narebski
2006-08-31 8:20 ` Thomas Glanzmann
2006-08-31 9:20 ` Jakub Narebski
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=200608310043.12606.jnareb@gmail.com \
--to=jnareb@gmail.com \
--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).