> -----Original Message----- > From: Gav.... [mailto:[EMAIL PROTECTED] > Sent: Sunday, 17 June 2007 8:09 AM > To: dev@forrest.apache.org > Subject: RE: [jira] Commented: (FOR-1011) ForrestBar search terms for > mail-archive.com need updating. > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > Brian M Dube > > Sent: Sunday, 17 June 2007 1:07 AM > > To: dev@forrest.apache.org > > Subject: Re: [jira] Commented: (FOR-1011) ForrestBar search terms for > > mail-archive.com need updating. > > > > On 6/16/07, Brian M Dube (JIRA) <[EMAIL PROTECTED]> wrote: > > > > > > [ https://issues.apache.org/jira/browse/FOR- > > 1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- > > tabpanel#action_12505491 ] > > > > > > Brian M Dube commented on FOR-1011: > > > ----------------------------------- > > > > > > See revisions 547646 and 547661. > > > > > > http://svn.apache.org/viewvc?view=rev&revision=547646 > > > http://svn.apache.org/viewvc?view=rev&revision=547661 > > > > The above comment is for future reference. What triggers Jira to link > > commits to issues? Is it mentioning FOR-1011 in the log message? > > > > Brian > > Yes it is , apologies for not doing that this time. > I can alter the log message to include it. > > Gav...
Ok, I have added the Forrest Issue FOR-1011 to each of those log messages, they 'should' appear on the Jira Issue soon, at least the log message refers back to the issue now. For what it's worth heres how I did it from Windows command line :- D:\Apache2\forrest>svn propedit svn:log --revprop -r547661 --editor-cmd edit https://svn.apache.org/repos/asf/forrest/trunk [the 'edit' editor opened up and I added FOR-1011 to the log message.] [I then saved the resultant temporary file] result output : Set new value for property 'svn:log' on revision 547661 I did that then for the other two log entries specifying the revision numbers. Gav...
