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. % svn log -r 430830:430856 ------------------------------------------------------------------------ r430853 | djd | 2006-08-11 20:41:09 +0200 (Fri, 11 Aug 2006) | 2 lines DERBY-1556 (partial) Add the initial implementation of a utility method in the JUnit JDBC class to drop a schema and all of its objects. Will be called by a test decorator I will be committing soon. ------------------------------------------------------------------------ r430855 | djd | 2006-08-11 20:48:59 +0200 (Fri, 11 Aug 2006) | 2 lines DERBY-1556 (partial) Add TODO's for the JDBC.dropSchema() method that shows work still needs to be done to drop function and synonyms. ------------------------------------------------------------------------ Rick, maybe you could generate these mega logs and update the log messages with "svn propedit svn:log --propedit -r N". -- Knut Anders
