tests: replace "cp -r" with "cp -R" The POSIX documentation about "cp" [1] says: .... RATIONALE .... Earlier versions of this standard included support for the -r option to copy file hierarchies. The -r option is historical practice on BSD and BSD-derived systems. This option is no longer specified by POSIX.1-2008 but may be present in some implementations. The -R option was added as a close synonym to the -r option, selected for consistency with all other options in this volume of POSIX.1-2008 that do recursive directory descent. The difference between -R and the removed -r option is in the treatment by cp of file types other than regular and directory. It was implementation-defined how the - option treated special files to allow both historical implementations and those that chose to support -r with the same abilities as -R defined by this volume of POSIX.1-2008. The original -r flag, for historic reasons, did not handle special files any differently from regular files, but always read the file and copied its contents. This had obvious problems in the presence of special file types; for example, character devices, FIFOs, and sockets. .... .... Issue 6 The -r option is marked obsolescent. .... Issue 7 .... The obsolescent -r option is removed. .... (No "Issue 8" yet) Therefore it's clear that "cp -R" is strictly better than "cp -r". The issue was discovered when running tests on OS X after 0d87b1caed92. [1]: pubs.opengroup.org/onlinepubs/9699919799/utilities/cp.html

     1

Initial setup.

     2

     3

  $ hg init repo

     4

  $ cd repo

     5

  $ touch thefile

     6

  $ hg ci -A -m 'Initial commit.'

     7

  adding thefile

     8

     9

Create a tag.

    10

    11

  $ hg tag branchortag

    12

    13

Create a branch with the same name as the tag.

    14

    15

  $ hg branch branchortag

    16

  marked working directory as branch branchortag

    17

  (branches are permanent and global, did you want a bookmark?)

    18

  $ hg ci -m 'Create a branch with the same name as a tag.'

    19

    20

This is what we have:

    21

    22

  $ hg log

    23

  changeset:   2:10519b3f489a

    24

  branch:      branchortag

    25

  tag:         tip

    26

  user:        test

    27

  date:        Thu Jan 01 00:00:00 1970 +0000

    28

  summary:     Create a branch with the same name as a tag.

    29

    30

  changeset:   1:2635c45ca99b

    31

  user:        test

    32

  date:        Thu Jan 01 00:00:00 1970 +0000

    33

  summary:     Added tag branchortag for changeset f57387372b5d

    34

    35

  changeset:   0:f57387372b5d

    36

  tag:         branchortag

    37

  user:        test

    38

  date:        Thu Jan 01 00:00:00 1970 +0000

    39

  summary:     Initial commit.

    40

    41

Update to the tag:

    42

    43

  $ hg up 'tag(branchortag)'

    44

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    45

  $ hg parents

    46

  changeset:   0:f57387372b5d

    47

  tag:         branchortag

    48

  user:        test

    49

  date:        Thu Jan 01 00:00:00 1970 +0000

    50

  summary:     Initial commit.

    51

    52

Updating to the branch:

    53

    54

  $ hg up 'branch(branchortag)'

    55

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    56

  $ hg parents

    57

  changeset:   2:10519b3f489a

    58

  branch:      branchortag

    59

  tag:         tip

    60

  user:        test

    61

  date:        Thu Jan 01 00:00:00 1970 +0000

    62

  summary:     Create a branch with the same name as a tag.

    63

    64

    65

  $ cd ..