Building with revision dependencies
See original GitHub issuearc patch help
implies that running it on a revision that depends on another should bring in the latest diff from the other, but it doesn’t seem to do that.
To support revision-on-revision testing, would it be easy to make the plugin pull in dependency revisions, or would it be better to make arc patch
to do that?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Maven issue to build one module using revision property
We tried to use: ... but the only thing that works is a build for parent that that builds the module and all...
Read more >Dependencies - Gentoo Development Guide
Build dependencies are used to specify any dependencies that are required to unpack, ... If at all possible, use the ~ form to...
Read more >TeamCity On-Premises - Build Dependencies Setup - JetBrains
This page gives the general idea on how dependencies work in TeamCity based on an example. For the dependencies' description, see Dependent Build....
Read more >Chromium Docs - Building old revisions - Google Git
Occasionally you may want to check out and build old versions of Chromium, ... When running gclient sync , also remove any dependencies...
Read more >dependency | Apache Ivy™ Documentation
Depending on the resolve mode used, the actual revision used during dependency resolution may vary. These revisions usually differ only for modules published...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nope. I assume Phabricator will provide a way to prune them at some point.
On Wed, Jul 27, 2016 at 9:46 AM Adam Chainz notifications@github.com wrote:
Good call, will overhaul docs in #154