atomicupdate: add an experimental option to use atomictemp when updating In some cases Mercurial truncating files when updating causes problems. It can happens when processes are currently reading the file or with big file or on NFS mounts. We add an experimental option to use the atomictemp option of vfs.__call__ in order to avoid the problem. The localrepository.wwrite seems to assume the files are created without the `x` flag; with atomictempfile, the new file might inherit the `x` flag from the destination. We force remove it afterward. This code could be refactored and the flag processing could be moved inside vfs. This patch should be tested with `--extra-config-opt experimental.update.atomic-file=True` as we disabled the option by default. Differential Revision: https://phab.mercurial-scm.org/D1882

     1

#ifndef _HG_MPATCH_H_

     2

#define _HG_MPATCH_H_

     3

     4

#define MPATCH_ERR_NO_MEM -3

     5

#define MPATCH_ERR_CANNOT_BE_DECODED -2

     6

#define MPATCH_ERR_INVALID_PATCH -1

     7

     8

struct mpatch_frag {

     9

	int start, end, len;

    10

	const char *data;

    11

};

    12

    13

struct mpatch_flist {

    14

	struct mpatch_frag *base, *head, *tail;

    15

};

    16

    17

int mpatch_decode(const char *bin, ssize_t len, struct mpatch_flist **res);

    18

ssize_t mpatch_calcsize(ssize_t len, struct mpatch_flist *l);

    19

void mpatch_lfree(struct mpatch_flist *a);

    20

int mpatch_apply(char *buf, const char *orig, ssize_t len,

    21

                 struct mpatch_flist *l);

    22

struct mpatch_flist *

    23

mpatch_fold(void *bins, struct mpatch_flist *(*get_next_item)(void *, ssize_t),

    24

            ssize_t start, ssize_t end);

    25

    26

#endif