monotone - Bugs: bug #15058, running "monotone...
You are not allowed to post comments on this tracker with your current authentication level.
bug #15058: running "monotone update" will delete removed files even if they are modified
Submitter: | None | ||
Submitted: | Fri 25 Nov 2005 06:28:23 AM UTC | ||
Category: | working copy | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: |
|
Thu 12 Aug 2010 11:09:48 AM UTC, comment #4: |
Stephen Leake <stephen_leake> |
Wed 11 Aug 2010 01:57:18 PM UTC, comment #3: Is this really fixed? The test in question is still shows the expected failure. |
Thomas Keller <tommyd> |
Thu 14 Aug 2008 11:17:09 PM UTC, comment #2: fixed in branch net.venge.monotone.automate_show_conflicts; it now reports a content/drop conflict. |
Stephen Leake <stephen_leake> |
Mon 04 Feb 2008 11:45:55 AM UTC, comment #1: Added unit test update_with_pending_modification, which checks for that bug. |
Markus Schiltknecht <markus_s> |
Fri 25 Nov 2005 06:28:23 AM UTC, original submission:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-02a9.
Corresponding source code
Clearly not fixed.
nvm.automate_show_conflicts only fixed stuff in merge, not update. So I must have been confused when I posted comment #2.
This will be fixed when I get around to improving update to handle conflicts properly.