Bug#876237: Doesn't display all commits

[Antonio Ospite]

On Sun, 4 Feb 2018 07:57:47 +1100
Carlos Maddela <e7appew at gmail.com> wrote:

> I'm not sure if this bug can be safely closed now, since I don't know if the
> behaviour I described previously was intended.
> 
> What has been resolved with the release of libgit2-glib/0.26.2-1 is that the
> 'Preferences' menu becomes available again in gitg, and you can choose
> the 'Show history in topological order' to restore the original behaviour in
> version 0.24.
> 

Sorry but I still see the issue with gitg, it can be replicated cloning
the repository mentioned in the upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=788090

Enabling topological order to fix the gitg issue is just a workaround.

My test case is a simple repository with only one branch, and gitg fails
to show all the commits, while the git command line tools work fine.

I am not sure if this is a libgit2 issue TBH, this simple pygit2 example
shows all the commits:

--------------------------------------------------------------------
#!/usr/bin/env python3

import pygit2

#mode = pygit2.GIT_SORT_NONE
#mode = pygit2.GIT_SORT_TOPOLOGICAL
mode = pygit2.GIT_SORT_TIME
#mode |= pygit2.GIT_SORT_REVERSE

repo = pygit2.Repository('.git')
for commit in repo.walk(repo.head.target, mode):
    print(commit.id, commit.message.split('\n')[0])
--------------------------------------------------------------------

Ciao,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?