On 2/22/07, William Uther <address@hidden> wrote:
The problem is in detecting if a file has changed. If you're using
compressed keywords in the database then manual expansion of those
keywords causes monotone to think the file has changed. If you're
not using compressed keywords in the database then you can do some
If there would be a hook that gets called before the SHAs get computed
on the workspace, that hook could remove the keyword expansions (in a
temporary file, obviously). Doesn't that solve the problem ? Or is
there also a concern of performance for large workspaces ?