Fossil SCM

[8a8685d103] and [058e287edb] both exhibit this issue.

[058e287edb] On merge, "fossil chan" properly displays changed files (2 files). "fossil revert ./onefile", and "fossil chan" displays no files. "fossil diff" displays no files.

[8a8685d103] On merge, (no "revert" applied), neither "fossil chan" nor "fossil diff" report what's expected.

bharder added on 2012-01-06 05:06:00 UTC: This buggy behaviour began at status improvements.

bharder added on 2012-01-06 06:30:34 UTC: See [d7ff893259] for branch w/ offending code removed (wholesale). Will need to be reviewed/replaced.

drh added on 2012-01-08 20:18:48 UTC: The status improvements was to fix an issue. Perhaps the fix was incorrect. But removing the fix is not right either. The right thing to do is to fix the fix.

Is there an easily reproducible test case that demonstrates the problem with status improvements?

bharder added on 2012-01-10 17:25:13 UTC:

Perhaps the fix was incorrect. But removing the fix is not right either.

I agree completely. What I've done here is provide a branch to isolate comparing these differences, and revert the way fossil behaves on the command line (by eliminating that original feature's side-effect); Am hoping to get the original fix back in, w/o it's side-effect, merge back to trunk.

bharder added on 2012-01-12 00:35:27 UTC: This change appears to work.