Hi Michael, please send all communication to the mailing list. Two things:
- Thanks for pointing out the naming convention in remote repositories. Scmbug should be corrected to support it. - 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". 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). In both cases, Scmbug hooks should be installed and be active. What do you think ? On Fri, 2010-02-12 at 11:05 +0300, Иванов Михаил wrote: > Hallo Kristis, > > 12.02.2010 00:26, Kristis Makris пишет: > > > First, scmbug_install_glue.pl needs to have local access to the GIT > > repository to install the hooks. It cannot install the hooks on a remote > > repository, because the Git protocol does not provide a means of doing > > so (e.g. like CVS does). > Yes, I am installing scmbug (and bugzilla) on the same machine where > my *remote* repository is located. > > > You said you have setup this repository. Have you tried running > > scmbug_install_glue.pl locally on the machine that hosts this > > repository ? > The repositary used as remote has slightly different structure > as compared to local. When I use local reposiotory it is expected > to bi in my work directory with '.git' name. Remote repositories > do not appear to have work directory, they are just named by project: > project1.git, project2.git and the contents of these directories > have the same structure as in .git directory in local repository. > > > It is not clear to me what is the proper model to use for integrating > > with a distributed version control system like Git. For example: > > > > - What should happen on the remote repository on a push operation ? > My impression is that actually scmbug should be connected to git > remote repository, not local. At least in my case I use the following > work pattern: > > edit and commit things in local repository. My local commits should > not be sent to bugzilla, since until I did not push them to central > repository I might reset or amend them. > > at some time I push my changes to remote. Here (ideally) it should > run each of my new commits through scmbug hook and treat it in a > regular way. > > The only problem here that I do not know exactly whether remote git > repository can reject individual commits during single push operation. > > > - What should happen on the local repository on a pull operation ? > > Should the pull be integrated with a local bug-tracker ? > Hm, should checkout be integrated with bugtracking at all? > Anyway my impression is only push operation is important. > And that in case a central repository is being used (like in my case), > scmbug hooks should be installed only on remote (central) repository > and never on local ones. > > 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
