MANIFEST.in
author maf46@burn.cl.cam.ac.uk
Mon, 04 Jul 2005 12:38:34 -0800
changeset 616 d45d1c90032e
parent 589 4be4d4580467
child 673 8e518e11f6cf
permissions -rw-r--r--
Fix zombie files in merge # HG changeset patch # User maf46@burn.cl.cam.ac.uk # Node ID 57667c9b93a5a743e4629d15a0e6bd76699130c3 # Parent d2994b5298fb20f87dc1d4747635b280db3c0526 Fix zombie files in merge Keir Fraser observed the following: > I made a small test case that illustrates the bug in merging changesets > with 'hg remove's in them: > > 1. Create a repository A containing files foo & bar. > 2. Create clone called B. > 3. A removes file bar, and commits this removal. > 4. B edits file foo, and commits this edit. > > Now, if B: > # hg pull ../A; hg update -m; hg commit > Then bar remains deleted. > > If A: > # hg pull ../B; hg update -m; hg commit > Then bar is resurrected! > > It looks as though, when you merge across a branch, any deletions in > your own branch are forgotten. > ... > Fixing this is a must, as zombie files are a real pain. :-) Keir later patched our local copy of hg as shown below, which fixes the problem. I've also enclosed a test which captures the test Keir outlined... Files deleted on a branch should not automatically reappear in a merge Patch notes: 1. The first chunk does not change behaviour, but cleans up the code to more closely match check of 'force' in the second chunk. I think it makes the code clearer. 2. The second chunk fixes two bugs -- i. If we choose to keep a remotely-changed locally-deleted file, then we need to 'get' that file. If we choose to delete it then no action need be taken (it is already deleted in the working manifest). Without this fix, choosing to delete would get a Python traceback. ii. The test for whether the file was remotely-created is insufficient. It is only true if f is not in the common ancestor. Otherwise the file was deleted locally, and should remain deleted. (this is the most important fix!) Index: hg/tests/test-merge6 ===================================================================
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
7
510265b68bbf Add MANIFEST.in to repo
mpm@selenic.com
parents:
diff changeset
     1
include hg
510265b68bbf Add MANIFEST.in to repo
mpm@selenic.com
parents:
diff changeset
     2
recursive-include mercurial *.py
188
f40273b0ad7b Mercurial 0.5
mpm@selenic.com
parents: 7
diff changeset
     3
include hgweb.cgi
589
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
     4
include hgeditor rewrite-log
457
12e0fdbc57a0 Release tweaks
mpm@selenic.com
parents: 448
diff changeset
     5
include tests/README tests/run-tests tests/test-*[a-z] tests/*.out
7
510265b68bbf Add MANIFEST.in to repo
mpm@selenic.com
parents:
diff changeset
     6
include *.txt
218
06bc1ef248a6 hgweb: put map-raw in setup.py and MANIFEST.in
mpm@selenic.com
parents: 188
diff changeset
     7
include templates/map templates/map-*[a-z]
188
f40273b0ad7b Mercurial 0.5
mpm@selenic.com
parents: 7
diff changeset
     8
include templates/*.tmpl
457
12e0fdbc57a0 Release tweaks
mpm@selenic.com
parents: 448
diff changeset
     9
include doc/README doc/*.txt
589
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
    10
include contrib/*
7
510265b68bbf Add MANIFEST.in to repo
mpm@selenic.com
parents:
diff changeset
    11
include README
589
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
    12
include CONTRIBUTORS
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
    13
include COPYING
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
    14
include TODO
4be4d4580467 [PATCH] bring MANIFEST.in up to date
mpm@selenic.com
parents: 457
diff changeset
    15
include MANIFEST.in