[dev-servo] Best way to work on multiple branches concurrently?

Hi, I often like to work on multiple branches concurrently, to work around the fact that Servo builds are slow. The obvious way to do this is to just have multiple clones. That's what I do with Firefox (using Mercurial). I've read that git 2.5 will have a `git checkout --to=path` command which wi

Re: [dev-servo] Best way to work on multiple branches concurrently?

Copy servobuild.example to .servobuild Then just add the path of a central .cargo or .servo to the cache-dir and cargo-home-dir keys. Mine are ./../.servo and ./../.cargo -Manish Goregaokar On Thu, Jun 11, 2015 at 1:26 AM, Nicholas Nethercote wrote: > Hi, > > I often like to work on multiple

Re: [dev-servo] Best way to work on multiple branches concurrently?

Cargo target-dir sharing (soon to be enabled by https://github.com/servo/servo/pull/6306) will also not rebuild dependencies that haven't changed. We could add the ability to put the target directory outside of the servo tree (it's a trivial change, and cargo already supports this). It actually may

Re: [dev-servo] Best way to work on multiple branches concurrently?

I personally keep the cargo dirs separate because Cargo doesn’t deal well with two concurrent runs, and I’m frequently developing and building in the two different clones at the same time. You *should* be able to share the rust/cargo snapshot directory without major concerns, though. On Jun 10,