No bugs in Gentoo, nothing serious upstream (https://bugzilla.gnome.org/buglist.cgi?quicksearch=gitg) Reproducible: Always
Err, 0.0.4, not 0.0.3, re-titling.
Minimal test scenario would be: - Clone a Git repo with many branches (git itself or linux kernel) - fire gitg up from the repo's folder - click around a bit :-)
Gitg-0.0.4 has several problems with stashes. If you create two stashes, removing the first one in Gitg results in an infinite loop, and removing the last one makes Gitg crash. I am using Gitg-0.0.5 for some weeks now, and it does not have these problems. Therefore, Gitg-0.0.5 seems to be the better candidate for stabilization. But I do realize that Gitg-0.0.5 was added to Portage only today.
amd64 done
(In reply to comment #3) > I am using Gitg-0.0.5 for some weeks now, and it does not have these problems. > Therefore, Gitg-0.0.5 seems to be the better candidate for stabilization. Sebastian, shall we go for 0.0.5 then in some weeks time?
(In reply to comment #5) > (In reply to comment #3) > > I am using Gitg-0.0.5 for some weeks now, and it does not have these problems. > > Therefore, Gitg-0.0.5 seems to be the better candidate for stabilization. > > Sebastian, shall we go for 0.0.5 then in some weeks time? Yeah. I haven't been using gitg with stashes so I didn't notice.
(In reply to comment #5) > shall we go for 0.0.5 then in some weeks time? I think that enough time has passed to reconsider the stabilization of Gitg-0.0.5. No bugs have been reported in Gentoo Bugzilla, and the upstream repository contains no significant changes. Please reopen.
Re-opening for 0.0.5 as requested.
x86 stable
amd64 stable, all arches done.
