From: Junio C Hamano Date: Sun, 22 Oct 2006 23:16:22 GMT Subject: Re: [PATCH] gitweb: Add "next" link to commitdiff view Message-ID: <7vd58k0wmx.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <200610230037.57183.jnareb@gmail.com> Jakub Narebski writes: > Add a kind of "next" view 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. > > Signed-off-by: Jakub Narebski 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.