Simon, Please forward all questions to the mailing list
On Tue, 2007-07-10 at 08:22 +0930, Maginnity, Simon (Contractor) wrote: > Okay thanks for the clarification. > > Yesterday I enetered a new bug into Bugzilla, bug 4: > > I then put some files up into subversion and put the following test log > message: > > "bug 4: Test Log Message - Fixes problem when the program sets the pump > pressure too high it blows out the oil seals. > [EMAIL PROTECTED]" > > After which I went back into bugzilla and hit refresh a few times > expecting to see some additional comments or something new. It did not > add this message into the additional comments as I thought it may. What > am I doing wrong, is this process already documented somewhere that I > have not read yet? Have you installed the integration glue ? If you were to e.g. enter no bug number at all, do you get an error by Scmbug that refuses to let the commit go through ? If you did install the glue, which version of Bugzilla are you using ? > Ta > > Simon > > -----Original Message----- > From: Kristis Makris [mailto:[EMAIL PROTECTED] > Sent: Monday, 9 July 2007 5:47 PM > To: Maginnity, Simon (Contractor) > Subject: Re: General question about scmbug > > Simon, > > I'm terribly sorry for the confusion. > > On Mon, 2007-07-09 at 10:40 +0930, Maginnity, Simon (Contractor) wrote: > > More just trying to work out exactly what it is that scmbug does. I > > cannot see where scmbug is adding the svn log information into > bugzilla. > > > > This email below is from one of my users. > > > > I don't believe that the intention is just to check syntax - it makes > > no sense. I do believe the intention is to annotate a bug entry in > > Bugzilla with details of what was changed in Subversion (ie, what > > changes did you make in order to fix the bug). I support my belief by > > > chapter 4.2 of the SCMbug manual (see below): > > This is correct. A user manually enters a log message, and Scmbug will > automatically detect the branch against which the changeset is applied, > produce the affected files list, and automatically add all that > information, along with the users original message, into the > bug-tracker. > > > I admit I don't know what is automatically or manually entered (ie, > > was all of the example message manually entered into the commit log of > > > Subversion, with the bug ID at the front of the message, or was some > > of the message generated by Subversion - eg affected files list), nor > > if there are intervening 'steps' > > So, somehow, any or all of us don't understand what's going on - and I > > > think it would be nice to clear it up - which I intend to do. > > I hope this clarifies things a little. Feel free to shot more questions > my way. > > Kristis > > > IMPORTANT: This email remains the property of the Australian Defence > Organisation and is subject to the jurisdiction of section 70 of the CRIMES > ACT 1914. If you have received this email in error, you are requested to > contact the sender and delete the email. > >
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
