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

Re: [PATCH] gitweb: Add "next" link to commitdiff view

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 29, 2006, 01:58 UTC
Message-ID
<200610290258.31771.jnareb@gmail.com>
In-Reply-To
<196807.75961.qm@web31801.mail.mud.yahoo.com>
Luben Tuikov wrote:
Show 15 quoted lines
> --- Jakub Narebski <jnareb@gmail.com> wrote:
>> Jakub Narebski wrote:
>>> 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.
[...]
Show 14 quoted lines
>> 
>> Any reasons not to accept this patch? I find it very useful.
>> 
>> The idea to use fixed string instead of shortened SHA-1 of commit
>> was abandoned after some discussion in this thread.
> 
> I prefer using the commit-8 without any "..." postfixed.  Anyone who
> knows squat about git knows very well what a commit-8 is when they
> see one -- the first 8 hexadecimal digits of the full SHA-1.
> 
> I like using "next" only when there is a "prev" right next to it,
> i.e. based on _context_, something like this:
>    << prev next>>
> where "<< prev" is hyperlinked, and "next>>" is also.

Unfortunately this is simply not possible in this case, as links in git are only from commit to paren(a), in one direction only.

Besides as you can see we can have more than one "next>>" link: for merge commit there are multiple parents. Well, for branch points there are multiple commits which have given commit as (one of) its parent(s), so there can be multiple "<<prev" links as well.

Show 5 quoted lines
> I looked at your patch (first email in this thread) and from
> what I gathered that it does, I like it (haven't tried it yet).
> 
> What I like about it is the clear information it conveys:
> it gives me both the commit-8 and what that commit-8 _is_.
It is commit-7, but that can be easily changed.
> Acked-by: Luben Tuikov <ltuikov@yahoo.com>
> (not that it matters in any way ;-) )
IIRC Junio asked for ACKs.
-- 
Jakub Narebski
Previous: Luben TuikovNext: Luben Tuikov
Message 4 of 6 in “Re: [PATCH] gitweb: Add "next" link to commitdiff view”
  1. Jakub NarebskiOct 28, 2006
  2. Junio C HamanoOct 28, 2006
  3. Luben TuikovOct 29, 2006
  4. Jakub NarebskiOct 29, 2006
  5. Luben TuikovOct 29, 2006
  6. Jakub NarebskiOct 29, 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.