{"push_id":1010067799,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d92aad7b30a426db8418d06632a67800397ce678","before":"8d52a6a3492cbf49354060a7bd80616fb2ed7f2a","commits":[{"sha":"d92aad7b30a426db8418d06632a67800397ce678","author":{"email":"82720107430038688f60cc7bc1f21e5cb3753f6e@gmail.com","name":"James Elford"},"message":"DROOLS-1082: Simplify the logic for how ClassAwareObjectStore manages its internal datastructures, and ensure the linked structure is properly updated when read and writes come out of order.\n\nThe problem was that the way the linking structure was put together went down a different branch depending on whether the nodes had already been initialized (e.g. by an earlier read). This change reduces the branching, so it's clearer what transformations need to be applied for each access.","distinct":true,"url":"https://api.github.com/repos/jelford/drools/commits/d92aad7b30a426db8418d06632a67800397ce678"}]}