<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ruuter.git/bench, branch v2.1.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git2.nmm.ee/ruuter.git/atom?h=v2.1.1</id>
<link rel='self' href='https://git2.nmm.ee/ruuter.git/atom?h=v2.1.1'/>
<link rel='alternate' type='text/html' href='https://git2.nmm.ee/ruuter.git/'/>
<updated>2026-04-10T12:55:56+00:00</updated>
<entry>
<title>Update Jank benchmark baseline and timer interop</title>
<updated>2026-04-10T12:55:56+00:00</updated>
<author>
<name>Asko Nõmm</name>
<email>asko@nmm.ee</email>
</author>
<published>2026-04-10T12:55:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git2.nmm.ee/ruuter.git/commit/?id=eb6f23ab6138cc132154145720c503d2509ede1f'/>
<id>urn:sha1:eb6f23ab6138cc132154145720c503d2509ede1f</id>
<content type='text'>
Refresh Jank benchmark numbers with the latest run and fix the Jank clock helper interop in the benchmark harness so future benchmark runs complete successfully.
</content>
</entry>
<entry>
<title>Add Jank support</title>
<updated>2026-02-17T21:03:14+00:00</updated>
<author>
<name>Asko Nõmm</name>
<email>asko@nmm.ee</email>
</author>
<published>2026-02-17T21:03:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git2.nmm.ee/ruuter.git/commit/?id=992210d3edca80df71689065178a2e5a1cfac009'/>
<id>urn:sha1:992210d3edca80df71689065178a2e5a1cfac009</id>
<content type='text'>
</content>
</entry>
<entry>
<title>2.0: Improve performance, usability.</title>
<updated>2026-02-17T18:29:53+00:00</updated>
<author>
<name>Asko Nõmm</name>
<email>asko@nmm.ee</email>
</author>
<published>2026-02-17T18:29:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git2.nmm.ee/ruuter.git/commit/?id=d3058cd7e742771d97ec81c9e4ae1e96f954d4a4'/>
<id>urn:sha1:d3058cd7e742771d97ec81c9e4ae1e96f954d4a4</id>
<content type='text'>
This is most likely a breaking change. Though from the API nothing
changes, behaviour does. It will no longer match routes based on
the first match, but rather the best match (the most specific route
wins).
</content>
</entry>
</feed>
