We're starting to use dependent revisions more with Differential (hg evolve is lovely and makes amending to non-head commits a cinch) - when moving between machines while working on revisions (or even having a peer patch down changes to test) a few update would make it more easily to patch down a string of revisions, make updates, diff back up, then switch back to another machine.
It's relevant to note that I use arc:bookmark as the base revision rule. I don't believe these features are dependent on this configuration.
See T12841 for an existing scenario where two revisions dependent revisions were created. I created two revisions D18122 (parent) and D18123 (child) and made the parent a dependency for the child.
- When patching a child revision, have bookmarks applied to other revisions that are patched in the process. So in the linked scenario also adding a bookmark arcpatch-D18122 to commit 22:c5421705ed9e since it was patched in the process of patching D18123.
- Use the last associated bookmark used by the revision instead of arcpatch-Dnnn if available. It looks like it's being tracked by the revision - you can see on D18122 that the bookmark I used was test. I'm guessing that one of the reasons arcpatch-Dnnn is used as it is unlikely collide with existing bookmarks, though there does appear to be fallback support for appending -1 if there is a collision.
- An option to not apply a bookmark when patching a revision. A few of my peers assume bookmarks are evil and prefer to type in numbers or something. They've mentioned that they end up with loads of arcpatch-Dnnn bookmarks that end up cluttering their repository. I'm pretty content with using bookmarks so I will have to investigate if further details are needed about these workflows.
- I believe in most of these cases no configuration for a base revision rule is set - I think they are passing mercurial changeset IDs to arc land or when specifying
- Automatically detecting dependency when creating a new revision with arc diff (I think this is T11343?)