Support platform-defined standard directories #5183

soc · Mar 15, 2018

This change stops cargo from violating the operating system rules
regarding the placement of config, cache, ... directories on Linux,
macOS and Windows.

Existing directories and overrides are retained.

The precedence is as follows:

use the CARGO_HOME environment variable if it exists (legacy)
use CARGO_CACHE_DIR, CARGO_CONFIG_DIR etc. env vars if they exist
use the ~/.cargo directory if it exists (legacy)
follow operating system standards

A new cargo command, dirs, is added, which can provide path
information to other command line tools.

Fixes:
#1734
#1976
rust-lang/rust#12725

Addresses:
rust-lang/rfcs#1615
#148,
#3981

rust-highfive · Mar 15, 2018

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

soc · Mar 15, 2018

Hi everyone, I would love to get some feedback on this (and I couldn't reach anyone at #cargo).
There are probably still things that are wrong and need to be adapted, but I'd like to get some feedback early.

soc · Mar 15, 2018

New cargo dirs command

Examples:

with existing .cargo directory

$ target/debug/cargo dirs
CARGO_CACHE_DIR:  "/home/soc/.cargo"
CARGO_CONFIG_DIR: "/home/soc/.cargo"
CARGO_DATA_DIR:   "/home/soc/.cargo"
CARGO_BIN_DIR:    "/home/soc/.cargo/bin"

without existing .cargo directory

$ target/debug/cargo dirs
CARGO_CACHE_DIR:  "/home/soc/.cache/cargo"
CARGO_CONFIG_DIR: "/home/soc/.config/cargo"
CARGO_DATA_DIR:   "/home/soc/.local/share/cargo"
CARGO_BIN_DIR:    "/home/soc/.local/bin/"

soc · Mar 15, 2018

soc reviewed Mar 15, 2018

View changes

soc · Mar 15, 2018

src/cargo/util/config.rs

+    // This is written in the most straight-forward way possible, because it is
+    // hard as-is to understand all the different options, without trying to
+    // save lines of code.
+    pub fn cargo_dirs() -> CargoDirs {


Should Config::cargo_dirs be renamed/moved to CargoDirs::new?

Yeah, new would looks slightly better I think, though current option is OK as well!

bors · Mar 15, 2018

☔️ The latest upstream changes (presumably #5176) made this pull request unmergeable. Please resolve the merge conflicts.

aturon · Mar 16, 2018

cc @nrc

matklad · Mar 17, 2018

matklad reviewed Mar 17, 2018

View changes

Overall, this looks great to me @soc!

One thing I am really worried about is how are we going to test this =/

we want to test it across at least mac/windows/linux (and probably on windows, there's also msvc/mingw/sigwin/linux subsystem axis?)
we want to test different fallback scenarios
we want to test this in conjunction with rustup

All this together implies to me that plain #[test] tests ain't gonna work here at all :(

I am thinking about a really heavy weight solution, like preparing docker images for different initial state of the machines, and then writing tests as bash scripts, which install rustup, create cargo project, etc. But, one does not simply create a docker image for windows I guess 🤷‍♂️ ?

It's also interesting that this PR actually does two things:

it refactors Cargo to support CargoDirs instead of monolithic CARGO_HOME.
it changes default locations for stuff, using directories and environment variables.

I wonder if it makes sense to split this over two pull request, and implement a refactoring first, while preserving current behavior fully. That way, we can separately check that the refactoring does not introduce regressions by itself, and then maximally concentrate on the fallback bits.

@rust-lang/cargo

matklad · Mar 17, 2018

src/cargo/ops/cargo_install.rs

@@ -122,7 +143,7 @@ pub fn install(
    if installed_anything {
        // Print a warning that if this directory isn't in PATH that they won't be
        // able to run these commands.
-        let dst = metadata(opts.config, &root)?.parent().join("bin");
+        let dst = metadata(opts.config, &Filesystem::new(root.config_dir))?.parent().join("bin");


This should be root.bin_dir I guess?

matklad · Mar 17, 2018

src/cargo/util/config.rs

+    // This is written in the most straight-forward way possible, because it is
+    // hard as-is to understand all the different options, without trying to
+    // save lines of code.
+    pub fn cargo_dirs() -> CargoDirs {


Yeah, new would looks slightly better I think, though current option is OK as well!

matklad · Mar 17, 2018

src/cargo/util/config.rs

+        let home_dir = ::home::home_dir().ok_or_else(|| {
+            format_err!("Cargo couldn't find your home directory. \
+                         This probably means that $HOME was not set.")
+        }).unwrap();


I think unwraps may panic in some obscure, yet real world scenario, so we really need proper error handlng. Changing the return type to CargoResult<CargoDirs> and replacing .unwraps with ? should do the trick I think?

As for an example of weird scenario, there were bug in Cargo about ::std::env::current_exe call failing, because Cargo was executed in chroot without procfs :)

matklad · Mar 17, 2018

src/cargo/util/config.rs

+        let mut cache_dir = cargo_dirs.cache_dir().to_path_buf();
+        let mut config_dir = cargo_dirs.config_dir().to_path_buf();
+        let mut data_dir = cargo_dirs.data_dir().to_path_buf();
+        // fixme: executable_dir only available on Linux, use data_dir on macOS and Windows?


This should be figured out in the RFC thread perhaps?

matklad · Mar 17, 2018

src/cargo/util/config.rs

+
+        // 3. .cargo exists
+        let legacy_cargo_dir = home_dir.join(".cargo");
+        if cargo_home_env.is_none() && legacy_cargo_dir.exists() {


This should be strictly a fall-back perhaps? That is, if all variables are not set, we set all dirs from .cargo, in contrast with the current per-dir approach?

matklad · Mar 17, 2018

src/cargo/util/config.rs

-    for current in paths::ancestors(pwd) {
-        let possible = current.join(".cargo").join("config");
+    for current in paths::ancestors(&dirs.current_dir) {
+        let possible = current.join(".cargo").join("config"); // fixme: what to do about this?


Nothing to be done here? It's an explicit feture of Cargo that it looks for .cargo/config in call parent directories. This exists for per-project .cargo dirs. Or am I missing something here?

Yes, I think you are right. I just wanted to be extra careful by marking all changes where I wasn't absolutely sure.

soc · Mar 17, 2018

@matklad Yes, testing is also a concern for me.

I think as a first step it would really help to have a list of different configurations and scenarios, so it is at least possible to test everything in an organized fashion, even if it is done manually.

I'm not sure whether splitting things into two commits makes sense, I feel that having an additional transitory state would have some benefits, but would also add overhead that would outweigh the benefits.

Especially because a similar PR needs to be done for rustup. With changes in one commit we would only have to test 4 different setups, {cargo: pre-change, post-change} * {rustup pre-change, post-change}.

With an additional state in the middle, this would balloon up to 9 different setups, for which all configurations and scenarios need to be tested against.

matklad · Apr 9, 2018

@soc have you managed to prepare a similar PR for rustup as well? I think updating rusupt would be a next step here, because we really do want to land changes to rustup and cargo simultaneously :)

soc · Apr 10, 2018

@matklad Not yet, but here is my plan:

I could really need some review of the current code to get a better understanding if this is the way people want to go (especially in regard to Path vs. Filesystem).
I would be thankful if someone has some time to look into the remaining test failures with me. I can make tests pass, but sometimes I'm not sure my changes to the tests are testing what was originally intended.
Implement changes in rustup.
Write some documentation that explains the changes.
Fix the existing documentation.
- Fix the official documentation.
- Fix third-party tutorials, blogs, StackOverflow, etc.
- Ping book authors.

matklad · Apr 11, 2018

matklad reviewed Apr 11, 2018

View changes

matklad · Apr 11, 2018

src/cargo/ops/cargo_install.rs

@@ -235,9 +256,9 @@ fn install_one(
    // We have to check this again afterwards, but may as well avoid building
    // anything if we're gonna throw it away anyway.
    {
-        let metadata = metadata(config, root)?;
+        let metadata = metadata(config, &Filesystem::new(dirs.config_dir.clone()))?;


It feels like metadata could perhaps be a method of CargoInstallDirs?

matklad · Apr 11, 2018

src/cargo/util/config.rs

+    pub cache_dir: Filesystem,
+    pub config_dir: Filesystem,
+    pub data_dir: PathBuf,
+    pub bin_dir: PathBuf,


It would be great to add short docstrings here, to explain which directory stores which data.

matklad · Apr 11, 2018

src/cargo/util/config.rs

@@ -32,22 +33,119 @@ use util::Filesystem;

 use self::ConfigValue as CV;

+#[derive(Clone, Debug)]
+pub struct CargoDirs {
+    pub home_dir: Filesystem,


We don't actually use this field I think?

matklad · Apr 11, 2018

src/cargo/util/config.rs

+        let home_dir = ::home::home_dir().ok_or_else(|| {
+            format_err!("Cargo couldn't find your home directory. \
+                         This probably means that $HOME was not set.")
+        })?;


So looks like we don't use home_dir for anything except fallback, so let's move this as far down as possible, so that we don't actually fail if HOME is not set, but explicit directories are! We might want to test this behavior as well: working without home directory is great for reproducible and isolated builds.

matklad · Apr 11, 2018

src/cargo/util/config.rs

+        #[cfg(target_os = "macos")]
+        let _bin_dir = cargo_dirs.data_dir().parent().map(|p| p.join("bin"));
+        #[cfg(target_os = "windows")]
+        let _bin_dir = cargo_dirs.data_dir().parent().map(|p| p.join("bin"));


Let's extract this into a function

#[cfg(os = )] fn bin_dir(dirs: &ProjectDirs) -> Option<PathBuf>

matklad · Apr 11, 2018

src/cargo/util/config.rs

        } else if let Some(val) = self.get_path("build.target-dir")? {
-            let val = self.cwd.join(val.val);
+            let val = self.dirs.current_dir.join(val.val);


Let's use self.cwd() here for future-proofing.

matklad · Apr 11, 2018

src/cargo/util/config.rs

-        let home_path = self.home_path.clone().into_path_unlocked();
-        let credentials = home_path.join("credentials");
+        let config_path = self.dirs.config_dir.clone().into_path_unlocked();
+        let credentials = config_path.join("credentials");


Hm, and what is the "correct" place for credentials? config might be not the right place, because people sometimes publish it... I suggest raising this question on the RFC thread, if it wasn't raised already.

matklad · Apr 11, 2018

src/cargo/util/config.rs

@@ -638,7 +736,7 @@ impl Config {
                None => false,
            };
            let path = if maybe_relative {
-                self.cwd.join(tool_path)


matklad · Apr 11, 2018

matklad reviewed Apr 11, 2018

View changes

matklad · Apr 11, 2018

tests/testsuite/login.rs

@@ -163,7 +163,7 @@ fn new_credentials_is_used_instead_old() {
        execs().with_status(0),
    );

-    let config = Config::new(Shell::new(), cargo_home(), cargo_home());
+    let config = Config::new(Shell::new(), CargoDirs::new().unwrap());


Here I think we want to point CargoDirs to CARGO_HOME inside test root.

One option is to provide another constructor for CargoDirs which accepts cargo_home: PathBuf. Another option is to modify the test such that it reads the config file directly. I am slightly in favor of the second approach.

matklad · Apr 11, 2018

matklad reviewed Apr 11, 2018

View changes

matklad · Apr 11, 2018

tests/testsuite/cross_compile.rs

@@ -910,7 +910,7 @@ fn build_script_needed_for_host_and_target() {
    );
 }

-#[test]
+//#[test]
 fn build_deps_for_the_right_arch() {


This actually passes for me locally

alexcrichton · Apr 11, 2018

r? @matklad

brson · Apr 16, 2018

So it's ok for rustup to disobey XDG even though everybody's all pissy that cargo doesn't? Doesn't really square.

brson · Apr 16, 2018

I would propose the exact opposite, namely trying to separate rustup and cargo as much as possible. Currently rustup installs its binaries in cargo's bin directory but I don't know of any good reason for that.

Because that's where your rust binaries live and it's on the PATH. All Rust binaries in one place.

brson · Apr 16, 2018

I'll think about it more, but if we really want CARGO_HOME to mean "everything here", then this patch has to change, and much of the strategy I wrote above, which I considered the simple way to modify rustup, is unworkable.

I also think you should go ahead and make rustup do the same thing with its directory structure while you are doing this - surely it'll just turn into another multi-year RFC fight for that if you don't.

brson · Apr 16, 2018

FWIW the RFC prioritizes XDG dirs over CARGO_HOME. It does seem to be easier to deprecate CARGO_HOME - leave it for the legacy toolchains, merge cargo and rustup into the same directory structure, and introduce RUST_HOME to mean "everything here".

OK, I'll stop talking now.

soc · Apr 16, 2018

@brson

I don't believe this is feasibile without seriously compromising what rustup is capable of. Would we really say "you can no longer use versions of Rust older than X?"; "you can't use new builds of Rust with an old rustup"?

But I'll be pretty disappointed if there's a big cutoff point where everything old breaks.

I think I worded it poorly, and believe we are on the same page considering the concerns you mentioned:

What I meant to say was that we have cut-off version, where everything before ends up in .cargo, and everything after uses the standard directories by default. I didn't want to imply that support for anything should be dropped, apologies if this caused some misunderstanding.

The idea was just to have that env var you suggested and keep testing things until everyone is confident that the changes are exactly what should be done, and have a separate switch date where the change is activated.

brson · Apr 16, 2018

Oh, regarding needing a new RUST_HOME dir to create self-contained installs, that isn't actually necessary, if the rustup changes incorporate my suggestion of recording the directory layout at install time - selecting a "self-contained" can just mean create a directory somewhere and setting all the various directories to values inside of it.

The only downside is that you can't do it through a single environment variable.

On the other hand, if you were to migrate rustup to integrate closer with cargo, you could just put all the rustup data inside the cargo data dirs, and an install with CARGO_HOME set would put everything in CARGO_HOME (again assuming you record the directory layout on install).

bors · Apr 22, 2018

☔️ The latest upstream changes (presumably #5407) made this pull request unmergeable. Please resolve the merge conflicts.

aturon · Apr 28, 2018

@brson I was away on vacation during your recent comments on this thread, but wanted to circle back and address them from a procedural/community perspective.

The very long initial comment you made interspersed a lot of potentially useful technical detail with some unconstructive critiques and re-litigation of the RFC. That's not an appropriate way to engage on a PR thread, especially with the passive-aggressive notes dropped throughout.

I'm grateful that @soc was willing to take it all in stride, but it's important that we all put in the effort to keep discussion constructive and helpful -- especially when such commentary is coming from project leaders, past or present.

soc · Jun 23, 2018

Just a heads up that I still intend working on this, I'm just blocked at the moment by some necessary changes in the supporting layers:

home_dir is broken and needs to be fixed: rust-lang/rust#51656
the APIs of dirs and directories need to change home_dir's result type from PathBuf to Option<PathBuf>
dirs and directories need to be relicensed to MIT/APL2
dirs and directories need a 1.0 release

soc · Jul 5, 2018

I addressed the four issues mentioned above, so these blockers are gone.

There are some small cleanups in dirs/directories (factor out common code) that I want to ship, but apart from that I'm good to go now.

alexcrichton · Jul 13, 2018

ping @matklad do you have a chance to take a look at this again?

matklad · Jul 13, 2018

Sure! This looks good to me in general, and I would be comfortable with merging it behind an unstable flag, if the following is done:

new behavior is actually hidden behind an unstable flag :-) The flag should be added over here. The end result should be that running cargo foo behaves exactly as today, and cargo -Z xdg foo uses new logic, with fallbacks and such.
directories dependency in Cargo.toml is updated to 1.0
There exact behavior is documented here. I understand that this is an unstable feature, but I think in this specific case it is important to get documentation together with the implementation, given the amount of subtitles, platform-specific behavior and the fact that RFC text lags behind the implementation. The docs would be in part a copy-paste of directories documentation of course, but it is important to keep this crate an implementation detail.
The behavior without the feature flag matches current behavior exactly. I'd love to help with auditing this, but I would prefer to do this after we have docs for the new behavior in place :)

alexcrichton · Oct 12, 2018

I'm going to close this because it's been stale and quiet for quite some time now unfortunately. The Cargo team is pretty tied up until after the 2018 edition, but I think we can perhaps look to help out integrating this and fixing remaining issues after the edition release.

flying-sheep · Jan 8, 2019

Hi! Rust 2018 is here, it’s a fresh new year! Time to get this rolling 😄

flying-sheep · Jan 8, 2019

Uh, how did I manage to unassign @matklad just by commenting‽

joshtriplett · Jan 9, 2019

joshtriplett reviewed Jan 9, 2019

View changes

joshtriplett · Jan 9, 2019

src/cargo/util/config.rs

+              && cargo_cache_env.is_none()
+              && cargo_config_env.is_none()
+              && cargo_data_env.is_none()
+              && cargo_bin_env.is_none() {


This doesn't seem to handle the case where some but not all of the environment variables are set.

joshtriplett · Jan 9, 2019

@soc Let's see if we can get this revived.

I posted one comment for a corner case this doesn't seem to handle.

Could you please update this to fix the conflicts, and ensure that it still passes tests?

And could you please add tests for the various configuration cases (existing legacy configuration, existing XDG configuration, both, no existing configuration), to make sure they all work as expected?

FranklinYu · Mar 31, 2019

I don’t like the solution for macOS. See soc/directories-rs#47.

soc · Mar 31, 2019

@joshtriplett Sorry for the late reply.

I think my changes so far are flawed in the sense that all the existing logic should be retained as-is, otherwise it becomes really really hard to make sure the current behavior is the same without flipping the hypothetical switch to the new structure.

Sadly, at the moment I have little time for this (and the website shenanigans didn't help either).

I can offer some advice, though: As a first step, identify each an every place in cargo, rustup, etc. that uses the current structure and add an explicit branch with a check for the proposed -Z flag there.

Then test that all tools reach the right branch when the flag is set/not set.

Only at this point it makes sense to even start working on the new structure

rust-highfive assigned alexcrichton Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from 6065027 to 390edbb Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from 390edbb to c192c7f Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from c192c7f to a290016 Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from a290016 to 0b350ad Mar 15, 2018

soc changed the title ~~[WIP] Add support for platform-defined standard directories~~ Add support for platform-defined standard directories Mar 17, 2018

soc force-pushed the soc:topic/standard-directories branch 4 times, most recently from cc80517 to 3aca0cf Mar 18, 2018

Eh2406 referenced this pull request Mar 28, 2018
Open
Support the XDG Base Directory Specification. #1734

matklad added the Rust-2018 label Mar 29, 2018

ehuss referenced this pull request Mar 31, 2018
Open
rfc: make cargo install extensible #2376

soc force-pushed the soc:topic/standard-directories branch 2 times, most recently from ff5e99a to bef5ad1 Apr 11, 2018

soc force-pushed the soc:topic/standard-directories branch from 750edc1 to 5d807d8 Apr 11, 2018

matklad referenced this pull request Apr 24, 2018
Open
Add flag to return cache directory #5412

soc force-pushed the soc:topic/standard-directories branch from 4baa882 to d3ffb18 Apr 28, 2018

soc referenced this pull request Jun 21, 2018
Merged
Deprecate `std::env::home_dir` and fix incorrect documentation #51656

reitermarkus referenced this pull request Sep 4, 2018
Merged
rust/cargo: enable caching #4815
6 of 6 tasks complete

alexcrichton closed this Oct 12, 2018

flying-sheep unassigned matklad Jan 8, 2019

joshtriplett reopened this Jan 9, 2019

dwijnand removed the Rust-2018 label Feb 11, 2019

nrc assigned joshtriplett Mar 6, 2019

rust-lang/cargo

Join GitHub today

Support platform-defined standard directories #5183

Conversation

soc commented Mar 15, 2018 • edited

rust-highfive assigned alexcrichton Mar 15, 2018

This comment has been minimized.

rust-highfive commented Mar 15, 2018

This comment has been minimized.

soc commented Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from 6065027 to 390edbb Mar 15, 2018

This comment has been minimized.

soc commented Mar 15, 2018 • edited

soc force-pushed the soc:topic/standard-directories branch from 390edbb to c192c7f Mar 15, 2018

soc reviewed Mar 15, 2018 View changes

This comment has been minimized.

This comment has been minimized.

soc force-pushed the soc:topic/standard-directories branch from c192c7f to a290016 Mar 15, 2018

This comment has been minimized.

bors commented Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from a290016 to 0b350ad Mar 15, 2018

This comment has been minimized.

aturon commented Mar 16, 2018

soc changed the title [WIP] Add support for platform-defined standard directories Add support for platform-defined standard directories Mar 17, 2018

matklad reviewed Mar 17, 2018 View changes

matklad left a comment

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

soc commented Mar 17, 2018 • edited

soc force-pushed the soc:topic/standard-directories branch 4 times, most recently from cc80517 to 3aca0cf Mar 18, 2018

Eh2406 referenced this pull request Mar 28, 2018

matklad added the Rust-2018 label Mar 29, 2018

ehuss referenced this pull request Mar 31, 2018

This comment has been minimized.

matklad commented Apr 9, 2018

This comment has been minimized.

soc commented Apr 10, 2018 • edited

soc force-pushed the soc:topic/standard-directories branch 2 times, most recently from ff5e99a to bef5ad1 Apr 11, 2018

matklad reviewed Apr 11, 2018 View changes

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

matklad reviewed Apr 11, 2018 View changes

This comment has been minimized.

matklad reviewed Apr 11, 2018 View changes

This comment has been minimized.

soc force-pushed the soc:topic/standard-directories branch from 750edc1 to 5d807d8 Apr 11, 2018

This comment has been minimized.

alexcrichton commented Apr 11, 2018

This comment was marked as disruptive content.

brson commented Apr 16, 2018

This comment has been minimized.

brson commented Apr 16, 2018

This comment has been minimized.

brson commented Apr 16, 2018

This comment has been minimized.

brson commented Apr 16, 2018 • edited

This comment has been minimized.

soc commented Apr 16, 2018 • edited

This comment has been minimized.

brson commented Apr 16, 2018 • edited

This comment has been minimized.

bors commented Apr 22, 2018

matklad referenced this pull request Apr 24, 2018

This comment has been minimized.

aturon commented Apr 28, 2018

soc force-pushed the soc:topic/standard-directories branch from 4baa882 to d3ffb18 Apr 28, 2018

soc referenced this pull request Jun 21, 2018

This comment has been minimized.

soc commented Mar 15, 2018 •

edited

soc force-pushed the soc:topic/standard-directories branch from `6065027` to `390edbb` Mar 15, 2018

soc commented Mar 15, 2018 •

edited

soc force-pushed the soc:topic/standard-directories branch from `390edbb` to `c192c7f` Mar 15, 2018

soc reviewed Mar 15, 2018

View changes

soc force-pushed the soc:topic/standard-directories branch from `c192c7f` to `a290016` Mar 15, 2018

soc force-pushed the soc:topic/standard-directories branch from `a290016` to `0b350ad` Mar 15, 2018

matklad reviewed Mar 17, 2018

View changes

soc commented Mar 17, 2018 •

edited

soc force-pushed the soc:topic/standard-directories branch 4 times, most recently from `cc80517` to `3aca0cf` Mar 18, 2018

soc commented Apr 10, 2018 •

edited

soc force-pushed the soc:topic/standard-directories branch 2 times, most recently from `ff5e99a` to `bef5ad1` Apr 11, 2018

matklad reviewed Apr 11, 2018

View changes

matklad reviewed Apr 11, 2018

View changes

matklad reviewed Apr 11, 2018

View changes

soc force-pushed the soc:topic/standard-directories branch from `750edc1` to `5d807d8` Apr 11, 2018

brson commented Apr 16, 2018 •

edited

soc commented Apr 16, 2018 •

edited

brson commented Apr 16, 2018 •

edited

soc force-pushed the soc:topic/standard-directories branch from `4baa882` to `d3ffb18` Apr 28, 2018

soc commented Jun 23, 2018 •

edited

joshtriplett reviewed Jan 9, 2019

View changes

joshtriplett commented Jan 9, 2019 •

edited