diff options
| author | Alasdair Nicol <alasdair@thenicols.net> | 2016-09-28 11:50:49 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-09-28 06:51:11 -0400 |
| commit | 63af78bbe01347539d311e7179d7744993d76bb6 (patch) | |
| tree | 8639e75fec6b28751c6f646d7a79a733c7c2513f | |
| parent | 933ebfad06b736e872b4c9afca6697cda8c3e216 (diff) | |
[1.10.x] Fixed 27283 -- Fixed typo in 1.8 release notes.
Backport of 32031718320e1b4d708b15d8c67738e4c77c9bc7 from master
| -rw-r--r-- | docs/releases/1.8.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index 706d2dc109..5cb91427c7 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -1187,7 +1187,7 @@ Miscellaneous Be careful if you upgrade to Django 1.8 and skip Django 1.7. If you run ``manage.py migrate --fake``, this migration will be skipped and you'll see a ``RuntimeError: Error creating new content types.`` exception because the - ``name`` column won't be dropped from the database. Use ``migrate.py migrate + ``name`` column won't be dropped from the database. Use ``manage.py migrate --fake-initial`` to fake only the initial migration instead. * The new :option:`migrate --fake-initial` option allows faking initial |