Fix bug attribution in changelog and mention #11

parent 34bed43e
...@@ -19,14 +19,16 @@ libvdp_pesi Changes ...@@ -19,14 +19,16 @@ libvdp_pesi Changes
NEXT NEXT
---- ----
.. !13 was a regression introduced since 7.2, so it does not qualify .. #13 was a regression introduced since 7.2, so it does not qualify
as a change herein as a change herein
* Implement ``onerror`` attribute like varnish-cache (`!11`_), except * Implement ``onerror`` attribute like varnish-cache (`#6`_), except
for one difference: Because pESI works in parallel, it runs into for one difference: Because pESI works in parallel, it runs into
errors earlier and thus may output less data than serial ESI in errors earlier and thus may output less data than serial ESI in
Varnish-Cache. Varnish-Cache.
* Fixed a panic when ``max_esi_depth`` was reached (`#11`_).
* Achieved an "all green" coverage report (>95% by lines, 100% by * Achieved an "all green" coverage report (>95% by lines, 100% by
functions) functions)
...@@ -38,7 +40,7 @@ NEXT ...@@ -38,7 +40,7 @@ NEXT
varnish-cache made it possible to avoid copying. varnish-cache made it possible to avoid copying.
* Fixed a bug which could surface as a panic when worker threads * Fixed a bug which could surface as a panic when worker threads
were destroyed (`!14`_) were destroyed (`#14`_)
* Improved documentation * Improved documentation
...@@ -48,8 +50,9 @@ NEXT ...@@ -48,8 +50,9 @@ NEXT
* Adjusted to vxid and other changes in varnish-cache * Adjusted to vxid and other changes in varnish-cache
.. _`!11`: https://gitlab.com/uplex/varnish/libvdp-pesi/-/issues/11 .. _`#6`: https://gitlab.com/uplex/varnish/libvdp-pesi/-/issues/6
.. _`!14`: https://gitlab.com/uplex/varnish/libvdp-pesi/-/issues/14 .. _`#11`: https://gitlab.com/uplex/varnish/libvdp-pesi/-/issues/11
.. _`#14`: https://gitlab.com/uplex/varnish/libvdp-pesi/-/issues/14
1097f6f48a8ea89fed89227965d94f630fb93c1f / 7.2 branch 1097f6f48a8ea89fed89227965d94f630fb93c1f / 7.2 branch
----------------------------------------------------- -----------------------------------------------------
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment