On 23/02/2007, at 10:14 AM, Hugo Cornelis wrote:
On 2/22/07, William Uther <[EMAIL PROTECTED]> 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 ?
There is a performance issue. There is also a security/consistency
issue. You want everyone on the same project using the same
transforms for consistency. But for security reasons you don't want
those hooks being run from the working copy.
Java hooks that run in a sandbox anyone? :-D
Will :-}
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
