- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 8 2020
After D12336:
Jun 7 2020
Jun 6 2020
Will this feature come to diffusion for audit workflows?
Jun 5 2020
Spaces have been working great for my install. The only real place where they're lacking I think arises from their coarseness/mutual-exclusivity.
Just extracting a few blocks of old code for reference:
I may actually make the minimum version whichever version has this fix:
Today, arc land in Mercurial does not support the "merge" land strategy.
I am dropping support for versions of Mercurial older than 2.1.1 (released in May, 2012). This is the first version that: (a) has phases and (b) does not exit 1 when hg pull succeeds but fetches no changes.
After changes connected to T13546, the git workflow now looks like this:
Jun 4 2020
After near-future changes connected to T13546 this is ripe for implementation, but I don't think it has come up again in ~6 years so I'm not sure it's actually worth improving. arc has also warned about abandoned revisions for a long time, which may have mooted this. My expectation is that the modern behavior is clear and the remedy is simple (arc land --revision 123) but I'm open to reconsidering this once the changes connected to T13546 have stabilized, if it's still an issue then.
After near-future changes connected to T13546, arc.land.onto (previously arc.land.onto.default) has higher priority than upstream branches.
Jun 3 2020
Jun 2 2020
See PHI1013, which would like a way to specify that the branch you want to merge into might be different from the name of the branch you want to push into the remote.
I think the general shape of this is:
