> -----Original Message----- > From: Ross Gardler [mailto:[EMAIL PROTECTED] > Sent: Friday, 11 August 2006 6:14 PM > To: dev@forrest.apache.org > Subject: Re: atomic commits (was: r430376 and r430377) > > David Crossley wrote: > > Gav.... wrote: > > > >>Yep, sorry about that. > > > > > > No worries, just helping to get you going smoothly. > > > > Another thing. Please try to add any relevant Jira issue > > numbers to the commit log message. > > For anyone who doesn't know why it may be worth a reminder... > > Adding FOR-200 to a commit log message, such as "did XYZ (FOR-200)" > will allow the commit to be crossrefenced in FOR-200 in the issue > tracker, as can be seen at the bottom of http://tinyurl.com/erxsu > > Ross
Thanks Guys for the Info, I did see this happening and should have followed Suit. I did however find a handy svn command and redeemed myself hopefully by Changing the log message to include the Jira Issue. Will Jira pick this Up now do you think ? Command used for ref :- svn propset -r 430376 --revprop svn:log "Changing ApacheCon images to load from locally resized images (FOR-907)" property 'svn:log' set on repository revision 430376 svn propset -r 430377 --revprop svn:log "ApacheCon images to go with commit 430376 (FOR-907)" property 'svn:log' set on repository revision 430377 Gav...
