https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271683
Jason E. Hale <jh...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jh...@freebsd.org
--- Comment #4 from Jason E. Hale <jh...@freebsd.org> ---
I've tried updating kommit to 1.3.1, which seems to run more efficiently and
not crash with large codebases, but a new arguably worse issue has cropped up
where all commit dates displayed are very close to the UXIX epoch i.e., every
commit in the repositories I've tested were all made in the month of January
1970 with various dates and timestamps, which is clearly erroneous.
Version 1.0.2 doesn't seem to have this problem, however. Upstream switched to
using libgit2 between releases and this new problem is probably related to
that, but I haven't confirmed it. If I get some time, I'll try to bisect the
code and see where things went awry.
There were no 1.1.x or 1.2.x releases tagged, BTW. 1.3.0 and 1.3.1 were tagged,
but no tarballs for either have been made publicly available AFAICT. Just going
off of what upstream git tells me. [1] Version 1.3.1 reports itself as 1.4.0,
as well.
[1] https://invent.kde.org/sdk/kommit/-/tags
--
You are receiving this mail because:
You are the assignee for the bug.
