Updated Issue 193 - Log and status of unknown file matching ignore list does not generate error (monotone)

Hello,

The following issue has been updated:

193 - Log and status of unknown file matching ignore list does not generate error
Project: monotone
Status: Fixed
Reported by: joe 23
URL: https://code.monotone.ca/p/monotone/issues/193/
Labels:
 Type:Defect
 Priority:Medium

Comments (last first):

# By Stephen Leake, Jun 23, 2012:

See new test status_of_ignored; it shows the expected behavior. 'mtn annotate restrictions.cc' shows the relevant fix was added to validate_paths in Feb 2008, for mtn 0.39.

 Status: Fixed

# By joe 23, Oct 14, 2011:

No error is generated if the file matches a pattern in the ignore list. The output makes it look like the file is in the db but has no log history. This is very confusing and difficult to diagnose.



Steps to reproduce the problem:
-------------------------------

1. > foo.bak
2. mtn status foo.bak
3. mtn log foo.bak

(actually, step 1 is not required, it does the same thing even if no file is present)


Expected result:
----------------
mtn: warning: restriction includes unknown path 'foo.bak'
mtn: misuse: 1 unknown path


Actual results:
---------------
(xxx shown for actual values)
status:


Revision: xxx
Parent:   xxx
Author:   xxx
Date:     xxx
Branch:   xxx

Changes against parent xxx

no changes


log:

o   (Revision: xxx)




Output of `mtn version --full`:
-------------------------------
1.0.0



--
Issue: https://code.monotone.ca/p/monotone/issues/193/