Thank you, Mark! That seemed to do the trick for the SVN log message. Just for reference, here's the command that I ended up submitting and it looks like it worked...
C:\>svn propset -r 1215255 --revprop svn:log "OPENJPA-2084. Committing the initial change to support the 10.8.2.2 version of derby. Additional changes for the documentation and possibly scripting changes will be coming shortly. These changes are being committed on behalf of Jacob Nowosatka. " https://svn.apache.org/repos/asf/openjpa/trunk property 'svn:log' set on repository revision 1215255 Now, I'll wait to see if the JIRA gets updated appropriately. But, at least the SVN history is now correct. Thanks again! Kevin On Thu, Dec 22, 2011 at 9:40 AM, Mark Struberg <[email protected]> wrote: > Hi Kevin! > > Please see the subversion docs on howto do this: > > > http://subversion.apache.org/faq.html#change-log-msg > > Guess a few folks on #asfinfra know how to do this properly. > > > LieGrue, > strub > > > > ----- Original Message ----- > > From: Kevin Sutter <[email protected]> > > To: [email protected] > > Cc: > > Sent: Thursday, December 22, 2011 4:04 PM > > Subject: Moving commit messages > > > > Hi, > > It looks like both Donald and I used the wrong JIRA when committing code > > for openjpa-2084 (we accidentally specified openjpa-2085). So, is there > a > > way to correct this mistake? We've added a comment to link the two > JIRAs, > > but it would be great if we could make the commit messages appear on the > > correct JIRAs. Thanks! > > > > Kevin > > >
