> > In both cases, Scmbug hooks should be installed and be active. > Should be or *might* be? As far as I understand I do not have to > install > hooks to all repositories I use. So if hooks are missing the only > consequence will be that I have to take care about notifying bugzilla > about my commits in some othe ways (if at all).
You are correct. You "might" want to have hooks. The issue raised here is that Scmbug should support some form of caching integration requests, just like the version control system is in a way caching commits to commit them later. We had at some point considered having a caching daemon, but later concluded that this is unnecessary. Because to do it right, any caching capability should be first supported by the version control system. With the same reasoning, one may want to also cache the issue-tracking system's data. And Scmbug needs both if it is to do any considerable policy checking. http://bugzilla.mkgnu.net/show_bug.cgi?id=1453 Thanks again for the feedback. These are good observations, and we haven't been challenged in our thinking of the model for Git. Please keep the feedback coming.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
