From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: <git@vger.kernel.org>
Subject: [PATCH 4/6] gitweb: Link to associated tree from a particular log item in full log view
Date: Fri, 22 Sep 2006 03:19:48 +0200 [thread overview]
Message-ID: <20060922011948.15909.59511.stgit@rover> (raw)
In-Reply-To: <20060922011941.15909.32671.stgit@rover>
Signed-off-by: Petr Baudis <pasky@suse.cz>
---
gitweb/gitweb.perl | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 0a91394..45a5fbf 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -2873,6 +2873,8 @@ sub git_log {
$cgi->a({-href => href(action=>"commit", hash=>$commit)}, "commit") .
" | " .
$cgi->a({-href => href(action=>"commitdiff", hash=>$commit)}, "commitdiff") .
+ " | " .
+ $cgi->a({-href => href(action=>"tree", hash=>$commit), hash_base=>$commit}, "tree") .
"<br/>\n" .
"</div>\n" .
"<i>" . esc_html($co{'author_name'}) . " [$ad{'rfc2822'}]</i><br/>\n" .
next prev parent reply other threads:[~2006-09-22 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 1:19 [PATCH 1/6] gitweb: More per-view navigation bar links Petr Baudis
2006-09-22 1:19 ` [PATCH 2/6] gitweb: Link to tree instead of snapshot in shortlog Petr Baudis
2006-09-22 1:19 ` [PATCH 3/6] gitweb: Link to latest tree from the head line in heads list Petr Baudis
2006-09-22 1:19 ` Petr Baudis [this message]
2006-09-22 4:18 ` [PATCH 4/6] gitweb: Link to associated tree from a particular log item in full log view Junio C Hamano
2006-09-22 23:13 ` Petr Baudis
2006-09-23 0:44 ` Junio C Hamano
2006-09-23 8:59 ` Jakub Narebski
2006-09-22 1:19 ` [PATCH 5/6] gitweb: Rename "plain" labels to "raw" Petr Baudis
2006-09-22 9:04 ` Jakub Narebski
2006-09-22 23:09 ` Petr Baudis
2006-09-22 1:19 ` [PATCH 6/6] gitweb: Relabel "head" as "HEAD" Petr Baudis
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=20060922011948.15909.59511.stgit@rover \
--to=pasky@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.