|
From: | Todd A. Jacobs |
Subject: | [Monotone-devel] sha1sum doesn't match revision number |
Date: | Thu, 1 Sep 2005 12:27:11 -0700 |
User-agent: | Mutt/1.5.9i |
I'm trying to implement monotone at work for tracking revisions to server configuration files, and keeping a repository on each server isn't an acceptable option (e.g. I can't treat the configurations files as a monotone working copy). So, the problem arises of trying to determine which revision the file on a given server represents.
Like I said, I tried the sha1sum approach, without luck. I know there was a suggested pre-commit hook to add some value to the file under revision control at commit time, but with these configuration files, that's not really an option.
How are other people currently handling this sort of issue? Or is it just outside the scope of what monotone is currently designed to address?
-- Re-Interpreting Historic Miracles with SED #141: %s/water/wine/g
[Prev in Thread] | Current Thread | [Next in Thread] |