<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/fs-mistrust/src, branch arti-v1.1.12</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-13T17:02:45Z</updated>
<entry>
<title>fs-mistrust: Explain where a Verifier comes from</title>
<updated>2023-12-13T17:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-12-07T15:42:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=93c664440a551f37cac4f975e10683c7d4c10de2'/>
<id>urn:sha1:93c664440a551f37cac4f975e10683c7d4c10de2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fs-mistrust: Add read_directory and remove_file to CheckedDir.</title>
<updated>2023-11-27T17:52:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-26T18:21:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d3e930ea8a62021c17873f46a5023e2f7cd77387'/>
<id>urn:sha1:d3e930ea8a62021c17873f46a5023e2f7cd77387</id>
<content type='text'>
Closes #1117.
</content>
</entry>
<entry>
<title>Run maint/add_warning to add lint block everywhere</title>
<updated>2023-08-23T09:34:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-22T14:28:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac'/>
<id>urn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run add_warnings on all files.</title>
<updated>2023-08-04T11:45:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-04T11:45:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cec6d0ce33b4b5cebbce57f55faec83397e9c953'/>
<id>urn:sha1:cec6d0ce33b4b5cebbce57f55faec83397e9c953</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run cargo +nightly fmt to format many let ... else ...</title>
<updated>2023-07-24T12:46:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-24T12:46:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3e2a909707acf7cad2621316a51f8643f1fe908a'/>
<id>urn:sha1:3e2a909707acf7cad2621316a51f8643f1fe908a</id>
<content type='text'>
rustfmt has grown opinions about how let ... else ... ought to be
formatted.  They don't always agree with our previous manual
decisions.

I think our policy is to always insist on rustfmt.  When that version
of rustfmt hits stable, our CI will start to fail for everyone.
(Right now this discrepancy just causes trouble for contributors who
are using nightly by default.)
</content>
</entry>
<entry>
<title>fs-mistrust: Run rustfmt to apply deferred formatting churn</title>
<updated>2023-07-14T15:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-14T14:10:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=967a36ee424aed0b0dbe216536990e7437e6b3a3'/>
<id>urn:sha1:967a36ee424aed0b0dbe216536990e7437e6b3a3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fs-mistrust: In a test, simplify env var handling</title>
<updated>2023-07-14T15:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-14T14:06:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f137cbbe7c4e1d660685934a53027956cb5120a2'/>
<id>urn:sha1:f137cbbe7c4e1d660685934a53027956cb5120a2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fs-mistrust: users: Use OsStr and OsString a lot less</title>
<updated>2023-07-14T15:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-14T14:01:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=792371a68867a27ad22cc473c613c9402b6c73c3'/>
<id>urn:sha1:792371a68867a27ad22cc473c613c9402b6c73c3</id>
<content type='text'>
We don't use OsString now except where it appears in our public API,
or where we get it from std::env.

Moving the `use` statements into the use sites enabled me to see
that I had found all the places I wanted to change.
</content>
</entry>
<entry>
<title>fs-mistrust: Remove a now-unneeded suppression</title>
<updated>2023-07-14T15:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-14T13:46:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5f3571fdf3e4c4dc732dec05453e15ef3ce06ed7'/>
<id>urn:sha1:5f3571fdf3e4c4dc732dec05453e15ef3ce06ed7</id>
<content type='text'>
This function is actually (properly) fallible now.
</content>
</entry>
<entry>
<title>fs-mistrust: forbid unsafe code</title>
<updated>2023-07-14T15:02:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-14T12:13:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=41543b06d67e55846cabe2ae773476510515227d'/>
<id>urn:sha1:41543b06d67e55846cabe2ae773476510515227d</id>
<content type='text'>
</content>
</entry>
</feed>
