[Python-modules-commits] r28607 - in packages/releases/trunk/debian (control)

[zyga-guest at users.alioth.debian.org]

    Date: Sunday, April 20, 2014 @ 20:30:01
  Author: zyga-guest
Revision: 28607

Reflow long description to fit under 80 columns

Modified:
  packages/releases/trunk/debian/control

Modified: packages/releases/trunk/debian/control
===================================================================
--- packages/releases/trunk/debian/control	2014-04-20 20:19:32 UTC (rev 28606)
+++ packages/releases/trunk/debian/control	2014-04-20 20:30:01 UTC (rev 28607)
@@ -31,11 +31,13 @@
  Specifically:
  .
    * The source format (kept in your Sphinx tree as ``changelog.rst``) is a
-     stream-like timeline that plays well with source control & only requires one
-     entry per change (even for changes that exist in multiple release lines).
-   * The output (when you have the extension installed and run your Sphinx build
-     command) is a traditional looking changelog page with a section for every
-     release; multi-release issues are copied automatically into each release.
+     stream-like timeline that plays well with source control & only requires
+     one entry per change (even for changes that exist in multiple release
+     lines).
+   * The output (when you have the extension installed and run your Sphinx
+     build command) is a traditional looking changelog page with a section for
+     every release; multi-release issues are copied automatically into each
+     release.
    * By default, feature and support issues are only displayed under feature
      releases, and bugs are only displayed under bugfix releases. This can be
      overridden on a per-issue basis.
@@ -56,11 +58,13 @@
  Specifically:
  .
    * The source format (kept in your Sphinx tree as ``changelog.rst``) is a
-     stream-like timeline that plays well with source control & only requires one
-     entry per change (even for changes that exist in multiple release lines).
-   * The output (when you have the extension installed and run your Sphinx build
-     command) is a traditional looking changelog page with a section for every
-     release; multi-release issues are copied automatically into each release.
+     stream-like timeline that plays well with source control & only requires
+     one entry per change (even for changes that exist in multiple release
+     lines).
+   * The output (when you have the extension installed and run your Sphinx
+     build command) is a traditional looking changelog page with a section for
+     every release; multi-release issues are copied automatically into each
+     release.
    * By default, feature and support issues are only displayed under feature
      releases, and bugs are only displayed under bugfix releases. This can be
      overridden on a per-issue basis.