Re: [Monotone-devel] Kicking around ideas

[Stephen Leake]

Thomas Keller <address@hidden> writes:

> I'm currently working on automate inventory (again) to fix certain
> issues which came up after I tried a test implementation for guitone.
> This is all about renames and the restricted output on those nodes.
>
> Consider the following workspace:
>
> $ mtn mkdir source
> $ touch source/a
> $ mtn add source/a && mtn ci
> $ mtn mv source target
>
> The current inventory implementation allows a path restriction only on
> nodes which actually exist, so while
>
> $ mtn au inventory target
>
> works,
>
> $ mtn au inventory source
>
> does not. 

It reports that "source" is not in the filesystem, so you can't
restrict the filesystem path to it. That seems reasonable.

> The latter was "fixed" by me already in
> 3a9c12f498b2446ff8b570ffc254367287203189 simply by adding another
> argument to the path_restriction ctor which optionally skips the
> path validity checks, but I think this is merely a hack.

Why would this be the right thing to do?

What is the user trying to accomplish?

If the user executed "mtn mv source target", but then forgot they did
that, the best solution is to do "mtn automate inventory" without a
restriction, to see the state of the entire tree.

-- 
-- Stephe