This is an automated email from the ASF dual-hosted git repository.
jdaugherty pushed a change to branch database-cleanup-feature
in repository https://gitbox.apache.org/repos/asf/grails-core.git
discard 730122d252 Add detailed timing to debug stats
discard 1a91738cdf Ensure cleanup runs even if the clean methods fail on the
spec
discard 67c5794562 Add postgresql clean up support
discard e9fcbdfd73 Add a new feature that assists in database truncation in
tests
add 8fad2d4803 Add a new feature that assists in database truncation in
tests
add 4b10c1dde7 Add postgresql clean up support
add 9d44bc0031 Ensure cleanup runs even if the clean methods fail on the
spec
add 47dfa5f836 Add detailed timing to debug stats
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (730122d252)
\
N -- N -- N refs/heads/database-cleanup-feature (47dfa5f836)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
