On Thursday 13 September 2007, William Uther wrote:
It seems the recent annotate changes in
ae0a9c829c508851a9bcfbcc22d6b088ab472ff6 don't pass the test suite.
Is this because the tests were broken too?
Broken is maybe too hard. Ralf brought back in sync the docs and mtn's
behavior for
Derek Scherger [EMAIL PROTECTED] writes:
Thomas Keller wrote:
Looks good. I did some small tweaks on the command line and version
display, but the rest seems to be fine. Just one thing hit my eyes:
Full support for versioned directories is not yet complete and the
inventory will only list
Derek Scherger [EMAIL PROTECTED] writes:
I vaguely recall some mention of a restricted inventory case where only
one side of a rename was listed in the inventory. Is there a test for
this?
Yes; see tests/automate_inventory_restricted/__driver__.lua, search
for the comment:
-- Rename a file
Derek Scherger [EMAIL PROTECTED] writes:
At a glance the docs look reasonable. I'm still not sure I prefer the
old_path and new_path stuff over the node id's though.
It's a compromise. Can you live with it?
Also, I see a FIXME in the docs for the invalid status
Yes, it needs a test. But
Derek Scherger [EMAIL PROTECTED] writes:
Stephen Leake wrote:
I have wondered about the proper format/content for changes in nvm.
I'd appreciate some written guidance in HACKING.
If nothing else the current ChangeLog file does give a bit of info about
this along with saying that it is no
Stephen Leake schrieb:
Derek Scherger [EMAIL PROTECTED] writes:
I vaguely recall some mention of a restricted inventory case where only
one side of a rename was listed in the inventory. Is there a test for
this?
Yes; see tests/automate_inventory_restricted/__driver__.lua, search
for the
I see this if I run an `mtn log` with a directory name I see output like this:
o-.-.-.-.-.-.-.-.-.-. (Revision: e6fcc2177d9e3fdc8f99dcc66fce3fc7e809d1d5)
|\ \ \ \ \ \ \ \ \ \ \
| | | | | | o | | | | |
-
| | | | | | | | |
