- I have a topic branch test branched off master
- It has 4 commits including a merge one from master
- There's an associated revision which is up-to-date (arc diff was called while on tip of topic branch)
- I then created a new topic branch off the tip of this topic branch and made a commit on it
arc which says it will update the revision instead of creating a new one.
Output of arc branch
$ arc branch test Needs Review D129: Testing things again master No Revision Fix * retest No Revision Update
Output of arc which
$ arc which REPOSITORY To identify the repository associated with this working copy, arc followed this process: Configuration value "repository.callsign" is empty. This repository has no VCS UUID (this is normal for git/hg). The remote URI for this working copy is "firstname.lastname@example.org:lifeonairteam/test.git". Found a unique matching repository. This working copy is associated with the Test repository. COMMIT RANGE If you run 'arc diff', changes between the commit: 3ab00423b0068413 Fix ...and the current working copy state will be sent to Differential, because it is the merge-base of 'origin/master' and HEAD, as specified in '.git/arc/default-relative-commit'. You can see the exact changes that will be sent by running this command: $ git diff 3ab00423b0068413..HEAD These commits will be included in the diff: 4def279945a7a890 Update e8eaafa0a61e27ed Fix be1bc08e863d9135 Merge branch 'master' into test 02e66df95f56950a Update b1867a16194702d9 Testing things again MATCHING REVISIONS These Differential revisions match the changes in this working copy: D129 Testing things again Reason: Commit message for 'b1867a16194702d9' has explicit 'Differential Revision'. Since exactly one revision in Differential matches this working copy, it will be updated if you run 'arc diff'.