<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-config/Cargo.toml, branch arti-v0.4.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-05-27T14:18:52Z</updated>
<entry>
<title>Regenerate version bump from previous commit.</title>
<updated>2022-05-27T14:18:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T14:18:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4326aa1de9875ea399c3a608c0320bbe4b214a42'/>
<id>urn:sha1:4326aa1de9875ea399c3a608c0320bbe4b214a42</id>
<content type='text'>
This commit was made by reverting the previous commit, then
re-running the script I used to generate it.  In theory there should
be no semantic changes: only changes due to improved formatting from
cargo edit.
</content>
</entry>
<entry>
<title>Semantic version changes for Arti 0.4.0 release</title>
<updated>2022-05-27T13:01:20Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T13:01:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b232365a75249d6f767127feb2a47286f9ece762'/>
<id>urn:sha1:b232365a75249d6f767127feb2a47286f9ece762</id>
<content type='text'>
I followed the following procedure to make these changes:

* I used maint/changed_crates to find out which crates had changed
  since 0.3.0.
* I used grep and maint/list_crates to sort those crates in
  topological (dependency) order.
* I looked through semver_status to find which crates were listed as
  having semver-relevant changes (new APIs and breaking changes).
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no changes.  For those crates, I incremented their patch-level
  version _without_ changing the version that other crates depend on.
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no obvious breaking changes.
* I treated all crates that depend on `arti` and/or `arti-client` as
  having breaking changes.
* I identified crates that depend on crates that have changed, even
  if they have not changed themselves, and identified them as having
  a non-breaking change.
* For all of the crates, I used `cargo set-version -p $CRATE --bump
  $STATUS` (where `STATUS` is `patch` or `minor`) to update the
  versions, and the depended-upon versions.
</content>
</entry>
<entry>
<title>tor-config: Example for load module</title>
<updated>2022-05-24T19:14:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-24T18:48:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9c88158740f85bd5a9c010947dc5707e897e5849'/>
<id>urn:sha1:9c88158740f85bd5a9c010947dc5707e897e5849</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Support functions for tracking ignored config keys</title>
<updated>2022-05-24T19:14:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-24T18:35:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=865ae13502e5f72b13f078dd5ab937742c34dff4'/>
<id>urn:sha1:865ae13502e5f72b13f078dd5ab937742c34dff4</id>
<content type='text'>
This turns out to need quite a complicated algorithm.
</content>
</entry>
<entry>
<title>arti-config abolition: Add deps to tor-config</title>
<updated>2022-05-13T11:41:27Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-13T10:27:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9a3205aeba665ad51b5c651bde657dbe9b9ebae0'/>
<id>urn:sha1:9a3205aeba665ad51b5c651bde657dbe9b9ebae0</id>
<content type='text'>
These are needed to support the code which is moving.
</content>
</entry>
<entry>
<title>arti-config: Move cmdline to tor-config</title>
<updated>2022-05-11T17:23:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-11T10:22:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ab3bd9d6d589cb23048603528913b375acfa8dd9'/>
<id>urn:sha1:ab3bd9d6d589cb23048603528913b375acfa8dd9</id>
<content type='text'>
This does not know anything about arti, only about TOML and Config.

Code motion, plus necessary import adjustments.
</content>
</entry>
<entry>
<title>Bump the version of every* crate to 0.3.0</title>
<updated>2022-05-06T14:03:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-06T14:03:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b93091f57f43ec8543a17052d60a2c8f7f2b0cc'/>
<id>urn:sha1:7b93091f57f43ec8543a17052d60a2c8f7f2b0cc</id>
<content type='text'>
* Except for safelog and fs-mistrust, which are new.
</content>
</entry>
<entry>
<title>Switch to derive_builder_arti_fork</title>
<updated>2022-05-06T12:36:40Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-06T12:18:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=030289481f79d7b1de4084e485b1793042b36ee8'/>
<id>urn:sha1:030289481f79d7b1de4084e485b1793042b36ee8</id>
<content type='text'>
For reference, the git source for this crate (and the others in its
workspace) currently lives in my personal github account (ijackson).
If this fork turns out to be long-lived and gains features and/or
users, it would be good to move it to a gitlab somewhere.

I have granted Nick crate ownership on the crates.io system.
</content>
</entry>
<entry>
<title>list_builder: Use Educe to derive Default</title>
<updated>2022-05-04T16:18:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-04T15:09:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=221fe634303271162e4fe7a83233d411ea5a582d'/>
<id>urn:sha1:221fe634303271162e4fe7a83233d411ea5a582d</id>
<content type='text'>
This allows us to use this with an item builder type which doesn't
impl Default.  (Obviously this only makes sense for items which aren't
actually builders.)
</content>
</entry>
<entry>
<title>Add dependency on paste crate</title>
<updated>2022-05-04T12:48:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-04-29T17:36:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8ad4735d5806611de04bf260c38c05d3d90df362'/>
<id>urn:sha1:8ad4735d5806611de04bf260c38c05d3d90df362</id>
<content type='text'>
The list accessor macro is going to want this.
</content>
</entry>
</feed>
