<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc/netstatus/build, branch arti-v1.7.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.7.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.7.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-10-22T13:18:04Z</updated>
<entry>
<title>tor-netdoc: Preamble: rename relay_version field to server_version</title>
<updated>2025-10-22T13:18:04Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-21T16:17:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=56929533b5e39e64c85b1697a5f9dcd4cd2d4193'/>
<id>urn:sha1:56929533b5e39e64c85b1697a5f9dcd4cd2d4193</id>
<content type='text'>
This makes it match the protocol and the spec.
</content>
</entry>
<entry>
<title>tor-netdoc: netstatus: Preamble: rename shared rand fields to match doc</title>
<updated>2025-10-22T13:17:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-21T11:43:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ac9af3273f12585bab50857f19124047098d2ff9'/>
<id>urn:sha1:ac9af3273f12585bab50857f19124047098d2ff9</id>
<content type='text'>
We should use the same name everywhere, even if the name in the spec
is clumsy (as it is here).
</content>
</entry>
<entry>
<title>tor-netdoc: Move ConsensusFlavor into Consensus struct</title>
<updated>2025-10-22T13:17:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-20T11:18:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=739f40ba7d628d2c860c141e1b093e2f0c6e3125'/>
<id>urn:sha1:739f40ba7d628d2c860c141e1b093e2f0c6e3125</id>
<content type='text'>
We're going to want to apply the parse2 derive to Preamble, but this
field is anomalous.  Rather than trying to make it regular, simply
move it to the old-parser-specific Consensus struct.
</content>
</entry>
<entry>
<title>tor-netdoc: Rename consensus Header to Preamble</title>
<updated>2025-10-22T13:17:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-20T11:06:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=009315256130d4c0150795844f927e07e52cc16e'/>
<id>urn:sha1:009315256130d4c0150795844f927e07e52cc16e</id>
<content type='text'>
There is no such thing as the "header" according to the spec.  We mean
the preamble.
</content>
</entry>
<entry>
<title>tor-netdoc: Change type of timestamp in SharedRandStatus</title>
<updated>2025-10-21T15:23:48Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-21T15:15:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3481970f543619b4b64ec3784136f7dc4b1455c6'/>
<id>urn:sha1:3481970f543619b4b64ec3784136f7dc4b1455c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Correct the headings of two modules</title>
<updated>2025-08-26T09:46:53Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-26T09:01:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=648a9fcd2cb918cf7f84e7961f5fefc5fc7b5bb6'/>
<id>urn:sha1:648a9fcd2cb918cf7f84e7961f5fefc5fc7b5bb6</id>
<content type='text'>
each_variety includes votes, so is "network status documents";
each_flavor is just consensuses.
</content>
</entry>
<entry>
<title>tor-netdoc: Move all each_variety code to each_flavor</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-21T10:30:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=03f69fca64d5a1b578a7941c29ad22c26ee19b3a'/>
<id>urn:sha1:03f69fca64d5a1b578a7941c29ad22c26ee19b3a</id>
<content type='text'>
The amount we're going to be able to reuse for votes is less than we
might hope.

This commit is just code motion.
</content>
</entry>
<entry>
<title>tor-netdoc: ns variety: Provide for flavour-only items</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T17:06:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1c2a90c2a4780fb1330ec21f8afec3009d6555c6'/>
<id>urn:sha1:1c2a90c2a4780fb1330ec21f8afec3009d6555c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Fix comments to refer to items</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T17:06:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d1e8810807adc4d9c0c5f210249c67f35b7448c5'/>
<id>urn:sha1:d1e8810807adc4d9c0c5f210249c67f35b7448c5</id>
<content type='text'>
It's not just types that can vary by variety.
</content>
</entry>
<entry>
<title>tor-netdoc: Fix some out-of-date comments</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T17:04:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fe490a80a2bcaab76aa7d5b9537f1153d5f37b86'/>
<id>urn:sha1:fe490a80a2bcaab76aa7d5b9537f1153d5f37b86</id>
<content type='text'>
We rename the files from per_ to each_.
</content>
</entry>
</feed>
