FYI -------- Forwarded Message -------- From: Иванов Михаил <[email protected]> To: Kristis Makris <[email protected]> Subject: Re: [scmbug-users] GIT glue installation Date: Fri, 12 Feb 2010 23:46:40 +0300
Hallo Kristis, 12.02.2010 21:04, Kristis Makris пишет: > - I don't agree with your opinion that local commits should not be > integrated with Scmbug (and possibly an issue-tracker). I believe Scmbug > should support such a behavior. Resetting or amending code changes is > part of the development process, and should be tracked. Of course, if > one doesn't want that integration, they can set the policy > "presence_of_bug_ids" to "none" or "optional". I just did not make myself clear on the issue. I was talking just about my specific case, where I (purely out of 'administrative' reasons) do not want scmbug hooks in local repositories. But of course there are cases when hooks are needed in local repository. > Similarly, I believe a pull should be integrated with bugtracking. > Bringing additional source into the local copy should be tracked (and > again could be disable using the "presence_of_bug_ids" policy). Let's put it 'can be tracked if so desired' :-) Again (maybe because I do not have very much experience with interfacing repositories to bugzilla) I do not see how it can be used in practice. > 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). Best regards,
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
