git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/1] gitweb: Use fixed string for "next" link in commitdiff view

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 23, 2006, 22:08 UTC
Message-ID
<200610240008.08325.jnareb@gmail.com>
In-Reply-To
<7vd58k0wmx.fsf@assigned-by-dhcp.cox.net>

Use fixed string instead of shortened SHA1 identifier of commit as a name for "mext" link in commitdiff view.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
Junio C Hamano wrote:
Show 23 quoted lines
> Jakub Narebski <jnareb@gmail.com> writes:
> 
>> Add a kind of "next" link in the bottom part of navigation bar for
>> "commitdiff" view.
>>
>> For commitdiff between two commits:
>>   (from: _commit_)
>> For commitdiff for one single parent commit:
>>   (parent: _commit_)
>> For commitdiff for one merge commit
>>   (merge: _commit_ _commit_ ...)
>> For commitdiff for root (parentless) commit
>>   (initial)
>> where _link_ denotes hyperlink. SHA1 is shortened to 7 characters on
>> display, everything is perhaps unnecessary esc_html on display.
> 
> Would it even be necessary to use any SHA-1 name in these cases,
> I wonder.  Would it make the page less useful if we replace all
> of the above _commit_ with a fixed string, say, "parent"?
> 
> I always hated gitweb diffs that prefix each filepair with their
> full 40-byte SHA-1 blob object names.  It just adds noise to the
> output without adding any meaningful information.

Here you have. I used patch on top of previous one instead of amending previous patch because I think it is interesting to have this history of this feature.

This patch doesn't add any functionality.
 gitweb/gitweb.perl |   16 ++++++----------
 1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 4241d5c..255487d 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -3291,15 +3291,11 @@ sub git_commitdiff {
 
 		if (defined $hash_parent) {
 			# commitdiff with two commits given
-			my $hash_parent_short = $hash_parent;
-			if ($hash_parent =~ m/^[0-9a-fA-F]{40}$/) {
-				$hash_parent_short = substr($hash_parent, 0, 7);
-			}
 			$formats_nav .=
-				' (from: ' .
+				' (' .
 				$cgi->a({-href => href(action=>"commitdiff",
 				                       hash=>$hash_parent)},
-				        esc_html($hash_parent_short)) .
+				        'from') .
 				')';
 		} elsif (!$co{'parent'}) {
 			# --root commitdiff
@@ -3307,19 +3303,19 @@ sub git_commitdiff {
 		} elsif (scalar @{$co{'parents'}} == 1) {
 			# single parent commit
 			$formats_nav .=
-				' (parent: ' .
+				' (' .
 				$cgi->a({-href => href(action=>"commitdiff",
 				                       hash=>$co{'parent'})},
-				        esc_html(substr($co{'parent'}, 0, 7))) .
+				        'parent') .
 				')';
 		} else {
 			# merge commit
 			$formats_nav .=
-				' (merge: ' .
+				' (' .
 				join(' ', map {
 					$cgi->a({-href => href(action=>"commitdiff",
 					                       hash=>$_)},
-					        esc_html(substr($_, 0, 7)));
+					        'parent');
 				} @{$co{'parents'}} ) .
 				')';
 		}
-- 
1.4.2.1
Previous: Jakub NarebskiNext: Petr Baudis
Message 5 of 16 in “gitweb: Add "next" link to commitdiff view”
  1. gitweb: Add "next" link to commitdiff viewJakub Narebski, Oct 22, 2006
  2. Jakub NarebskiOct 22, 2006
  3. Junio C HamanoOct 22, 2006
  4. Jakub NarebskiOct 22, 2006
  5. 2/1 gitweb: Use fixed string for "next" link in commitdiff viewJakub Narebski, Oct 23, 2006
  6. Petr BaudisOct 23, 2006
  7. 2/1 gitweb: Use fixed string for "next" link in commitdiff viewJakub Narebski, Oct 24, 2006
  8. Junio C HamanoOct 24, 2006
  9. Jakub NarebskiOct 24, 2006
  10. Petr BaudisOct 24, 2006
  11. Jakub NarebskiOct 24, 2006
  12. Petr BaudisOct 24, 2006
  13. Junio C HamanoOct 24, 2006
  14. Petr BaudisOct 24, 2006
  15. Junio C HamanoOct 24, 2006
  16. Jakub NarebskiOct 24, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.