Re: [Monotone-devel] Tailor

[Brian May]

>>>>> "Nathaniel" == Nathaniel Smith <address@hidden> writes:

    Nathaniel> filesystem thinks.  Since filesystems are horrible
    Nathaniel> creatures full of race conditions, this can be tricky.
    Nathaniel> The most common problem, and the one you ran into here,
    Nathaniel> is that a directory may contain unversioned files that
    Nathaniel> are "invisible" to monotone.  When monotone attempts to

Speaking of race conditions, I think we just encountered one - I just
posted much the same thing myself ;-).

    Nathaniel> apply a changeset to the workspace that removes that
    Nathaniel> directory, it eventually notices the problem when it's
    Nathaniel> already in the middle of its work.  At that point it
    Nathaniel> basically can either silently trash all those
    Nathaniel> sunversioned files, or error out, leaving the workspace
    Nathaniel> in an inconsistent state.  We do the latter.

    Nathaniel> Better would be to have some sort of rollback, or
    Nathaniel> moving the offending files out of the way while
    Nathaniel> preserving them, or something like that...  but getting
    Nathaniel> a general solution is difficult, and no-one has worked
    Nathaniel> out a design yet.  Some of the ideas that might be
    Nathaniel> helpful are on the wiki:
    Nathaniel> http://venge.net/monotone/wiki/CaseInsensitiveFilesystems
    Nathaniel> http://venge.net/monotone/wiki/Win32DeviceFiles
    Nathaniel> http://venge.net/monotone/wiki/NonMergeConflicts

Yes. My preference would be rollback + good error message.

Also the message could be improved - perhaps even displaying where the
directory use to be located for instance...

Some files are just junk files - would the same thing happen for *.bak
files?
-- 
Brian May <address@hidden>