Knut Anders Hatlen wrote: > Daniel John Debrunner <[EMAIL PROTECTED]> writes: > > >>[EMAIL PROTECTED] wrote: >> >> >>>Author: rhillegas >>>Date: Fri Aug 18 10:09:04 2006 >>>New Revision: 432641 >>> >>>URL: http://svn.apache.org/viewvc?rev=432641&view=rev >>>Log: >>>DERBY-1725: Merge trunk into 10.2 branch from 430830 through 430856. >> >>This is a problem with the mega merges, we lose the linkage to the >>individual Jira entries. Had the svn log message contained the Jira >>issue numbers for the changes in that range, then it would be easy to >>tell from an individual Jira entry if the change made it into 10.2 or not. > > > It would be good to run "svn log" with the revision range and add the > output to the log message for the mega merge. >
> Rick, maybe you could generate these mega logs and update the log > messages with "svn propedit svn:log --propedit -r N". > +1 Great idea - simple to do! Dan.
