tests/test-merge4.t
author Boris Feld <boris.feld@octobus.net>
Wed, 03 Oct 2018 11:04:57 +0200
changeset 40551 4dd7edeb3da9
parent 16536 63c817ea4a70
child 44343 8561ad49915d
permissions -rw-r--r--
perf: offer full details in perfrevlogwrite This will be useful for people who want to study the timing pattern more closely.

  $ hg init
  $ echo This is file a1 > a
  $ hg add a
  $ hg commit -m "commit #0"
  $ echo This is file b1 > b
  $ hg add b
  $ hg commit -m "commit #1"
  $ hg update 0
  0 files updated, 0 files merged, 1 files removed, 0 files unresolved
  $ echo This is file c1 > c
  $ hg add c
  $ hg commit -m "commit #2"
  created new head
  $ hg merge 1
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)
  $ rm b
  $ echo This is file c22 > c

Test hg behaves when committing with a missing file added by a merge

  $ hg commit -m "commit #3"
  abort: cannot commit merge with missing files
  [255]