Displaying 4 results from an estimated 4 matches for "d8811c90".
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
...-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250408/d8811c90/attachment.htm>
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
...-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250408/d8811c90/attachment.htm>
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing.
There are commits in the rc tag that are not on master:
$ git log --oneline ..v2.8.3-rc1
3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches
4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches
504706d45 Makefile.am: nut-scanner does directly depend on clients after all
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing.
There are commits in the rc tag that are not on master:
$ git log --oneline ..v2.8.3-rc1
3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches
4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches
504706d45 Makefile.am: nut-scanner does directly depend on clients after all