In D12627#193350, @Alphare wrote:@mharbison72 you should have no trouble at all since you're already using Hetpapod for the CI. Please read the contributor guide here: https://www.mercurial-scm.org/wiki/Heptapod
I hope I'm clear, it's very late and my brain is half-working. :)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Today
Today
mharbison72 added a comment to D12627: worker: adapt _blockingreader to work around a python3.8.[0-1] bug (issue6444).
What Are The Boating Essentials?
5 Must-Have Boating Accessories
Top Brands On Marine Supplies US
baymax added a comment to D12619: auto-upgrade: skip the operation if the repository cannot be locked.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12618: auto-upgrade: add a test case where the repository is already locked.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12616: debuglock: make the command more useful in non-interactive mode.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12613: auto-upgrade: introduce a way to auto-upgrade to/from tracked-hint.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax retitled D12617: wait-on-file: properly wait on any files and symlink from wait-on-file: properly wait on any file and symlink to wait-on-file: properly wait on any files and symlink.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12611: auto-upgrade: introduce a way to auto-upgrade to/from share-safe.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12614: auto-upgrade: introduce a way to auto-upgrade to/from dirstate-v2.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
baymax updated the summary of D12615: auto-upgrade: add a test case with no permission to lock the repository.
✅ refresh by Heptapod after a successful CI run (🐙 💚)
✅ refresh by Heptapod after a successful CI run (🐙 💚)
In D12623#193297, @aalekseyev wrote:I'll remove a hardlink=True comment (which is not really worthy of a phabsend), but I don't understand the purpose of the split between (1) and (2). The only reason we're removing a directory is that we're creating it and putting temp files there.
Actually, a commit message could be improved...
ci: have rust-cargo-test inherit from all
copies-sdc: mark upgrade action as changelog only
changelog-v2: mark upgrade action as changelog only
copies-sdc: no longer suppress the upgrade output
marmoute committed rHGeb5954f092a9: copies-sdc: no longer use revlogv2 in `test-copies-in-changeset.t`.
copies-sdc: no longer use revlogv2 in `test-copies-in-changeset.t`