Thanks z for the report and timo for the proposal.

This reverts commit 4fdd51b7.

See the ticket for concerns with this implementation; it will be revisited.

Thanks Peter Landry for the report.

Fix a typo in logging.txt

Thanks nliberg for the suggestion.

Thanks Karen Tracey for the report.

Thanks kevin-brown for the report.

Thanks Eric Holscher and Tim Graham for the review.

Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.

Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.

sqlparse becomes mandatory for RunSQL on some databases (all but
PostgreSQL). There's no API to provide a single statement and tell
Django not to attempt splitting. Since we have a more robust splitting
implementation, that seems like a good tradeoff. It's easier to add a
new keyword argument later if necessary than to remove one.

Many people contributed to both tickets, thank you all, and especially
Claude for the review.

Refs #22401.

Refs #22422.

Thanks chris at chrullrich.net.

Thanks Erik Romijn for the suggestion.

Fixed #22515 -- Fixed the object_id of the LogEntry that's created after a user password change in the admin.

Thanks ross at servercode.co.uk for the report.

Refs #22496.

Refs #22483

Fixed #22483 (again).

Forwardport of 5cd64296 from stable/1.7.x

Forwardport of 9bbb43dd from stable/1.7.x

See also http://blog.transifex.com/post/83622601443/new-teams-management-transifex

- Fixed bug in get_callable() that caused resolve() to put a string
  in ResolverMatch.func.
- Made ResolverMatch.url_name match the actual url name (or None).
- Updated tests that used the string value in ResolverMatch.func, and
  added regression tests for this bug.
- Corrected test urls whose dummy view paths caused failures (behavior
  that was previously masked by this bug).

Since all state is maintained on the connection at this time and none in
the atomic, it doesn't matter, but it could introduce some subtle bugs
if the implementation changed in the future.

Refs #18714. Same logic as options for makemessages commands.

cache.add() incorrectly succeeded when there was an existing key
with an infinite (None) timeout.

Refs #22451.