Page MenuHomePhabricator

Updating a revision with dependencies pulls all diffs from dependencies by default
Closed, ResolvedPublic


At least for Mercurial-based repos, if revision B depends on A, modifying B and running "arc diff" will put the changes from A into the revision for B. While this can be easily worked around by specifying the base commit, it would be preferable if arcanist/phabricator determined the base commit for B by default.

Event Timeline

bubble-07 raised the priority of this task from to Needs Triage.
bubble-07 updated the task description. (Show Details)
bubble-07 added a subscriber: bubble-07.

Use arc which to understand what arc is doing and why.

I believe the behavior as described is (currently) expected with Mercurial. To update revision B without A's changes you must specify the commit from A to B, otherwise it will default to the range from master to B which will include A's changes.

epriestley claimed this task.

See T6072 / T11356 for discussion.