[Monotone-commits-diffs] net.venge.monotone: 365dd6645b59c22a23889c01a6b5e632ff2d3e8d

[code]

revision:            365dd6645b59c22a23889c01a6b5e632ff2d3e8d
date:                2012-06-23T19:35:20
author:              address@hidden
branch:              net.venge.monotone
changelog:
* test/func/status_of_ignored: New directory, for issue 193

manifest:
format_version "1"

new_manifest [d93cc0c01fdec136a67a76db495c740c26ec79ab]

old_revision [6968a970de870ce2c72458723b8798f54f590525]

add_dir "test/func/status_of_ignored"

add_file "test/func/status_of_ignored/__driver__.lua"
 content [f64919f41c4733dac61b88884b945988faa1c2b0]
============================================================
--- /dev/null	
+++ test/func/status_of_ignored/__driver__.lua	f64919f41c4733dac61b88884b945988faa1c2b0
@@ -0,0 +1,27 @@
+-- Test for issue 193
+--
+-- Original problem:
+--
+-- mtn status foo.bak produces confusing output, assuming '*.bak' is
+-- in the list of ignore file patterns (it is in the default list).
+--
+-- The problem report states this was noticed in mtn 1.0 (released
+-- in 2011), but annotate says the relevant fix was added in 2008.
+
+mtn_setup()
+
+-- add a real file, to see what a 'normal' status report looks like
+addfile("file_1", "file_1")
+commit()
+
+check(mtn("status", "file_1"), 0, true, nil)
+check(qgrep("no changes", "stdout"))
+
+-- Now gives an error:
+check(mtn("status", "foo.bak"), 1, nil, true)
+check(qgrep("warning: restriction includes unknown path 'foo.bak'", "stderr"))
+
+-- Try again with an existing foo.bak
+writefile("foo.bak", "foo.bak")
+check(mtn("status", "foo.bak"), 1, nil, true)
+check(qgrep("warning: restriction includes unknown path 'foo.bak'", "stderr"))