On 24 Dec 2010, at 16:43, Gary L. Wade wrote: > Source control systems may modify hidden files locally when performing a > commit; some have historically utilized the resource fork of the particular > file instead to keep that commit/modified state. Still others may choose to > use an xattr to track this. > > The bottom line is that the only real guarantee of a file being changed > during a commit is within the repository of a source control system, not your > local sandbox.
In particular, you should take advantage of any hooks offered by the VCS. Google suggests that CVS has some hooks called after commits are made, which sounds ideal. Cheers, Chris _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
