Bug#1020180: bug 1020180 is forwarded to https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3
On Thu, Nov 17, 2022 at 05:23:16PM -0500, Nicholas D Steeves wrote:
> Adrian Bunk <bunk@debian.org> writes:
>
> > forwarded 1020180 https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3
> > thanks
>
> Thank you for setting this metadata, and for finding the specific commit
> :)
>
> I've leaning towards packaging a git snapshot, and then encouraging
> upstream to make a release if it seems release-candidate-like, because
> then our source will be closer to upstream. Of course, ideally we'll
> have a tagged release in bookworm, Also, upstream hasn't made a release
> in over 18 months, and abo-abo, the primary developer hasn't been heard
> from in something like a year,
https://github.com/abo-abo/swiper/commit/e32289080957e4f6ee48dcb879c437eea62a1133
ivy.el (ivy-occur-flush-lines): Add
master
abo-abo committed Sep 10, 2022
> so I think upstream may appreciate the vote of confidence!
Upstream might not appreciate people complaining for years about a buggy
git snapshot of the software in a stable Debian release.
> What do you think?
I cannot give an informed opinion on that for a software I do not use,
maintained by an upstream I do not know.
Are there other fixes relevant for Emacs 28 in upstream git?
What quality are releases of this software usually?
What quality are git snapshots of this software usually?
> Kind regards,
> Nicholas
cu
Adrian
Reply to: