https://defect.opensolaris.org/bz/show_bug.cgi?id=19116
Knut Anders Hatlen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ACCEPTED |CLOSED Resolution| |FIXED Target Milestone|--- |next --- Comment #2 from Knut Anders Hatlen <[email protected]> 2011-12-27 08:44:49 UTC --- Judging by the code and the unit tests, splitting of changesets like the one mentioned above, was intentional. With the flat file history backend, the duplicates won't be noticed, and the creation of the history cache will be successful. However, the revision numbers in the split changeset point to revisions in another branch, so choosing any of those changesets (or diffing them) in the history view won't work as expected. They'll instead show the revisions with that revision number in the branch that has been checked out. With the JDBC history cache backend, it fails earlier because it has checks on insert for duplicate revision numbers. So it seems like not splitting these changesets would be the right thing to do for both the backends. Checked in a fix: changeset: 1285:fbd6940954e7 -- Configure bugmail: https://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ opengrok-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
