windows: sanity-check symlink placeholders On Windows, we store symlinks as plain files with the link contents. Via user error or NFS/Samba assistance, these files often end up with 'normal' file contents. Committing these changes thus gives an invalid symlink that can't be checked out on Unix. Here we filter out any modified symlink placeholders that look suspicious when computing status: - more than 1K (looks more like a normal file) - contain NULs (not allowed on Unix, probably a binary) - contains \n (filenames can't contain \n, very unusual for symlinks, very common for files)

     1

Test issue2761

     2

     3

  $ hg init

     4

     5

  $ touch to-be-deleted

     6

  $ hg add

     7

  adding to-be-deleted

     8

  $ hg ci -m first

     9

  $ echo a > to-be-deleted

    10

  $ hg ci -m second

    11

  $ rm to-be-deleted

    12

  $ hg diff -r 0

    13

    14

Same issue, different code path

    15

    16

  $ hg up -C

    17

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

    18

  $ touch doesnt-exist-in-1

    19

  $ hg add

    20

  adding doesnt-exist-in-1

    21

  $ hg ci -m third

    22

  $ rm doesnt-exist-in-1

    23

  $ hg diff -r 1