Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-commits
Navigation:
Lists: gentoo-commits: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-commits@g.o
From: "Paul Varner (fuzzyray)" <fuzzyray@g.o>
Subject: gentoolkit r482 - trunk/src/echangelog
Date: Fri, 14 Mar 2008 14:26:54 +0000
Author: fuzzyray
Date: 2008-03-14 14:26:53 +0000 (Fri, 14 Mar 2008)
New Revision: 482

Modified:
   trunk/src/echangelog/echangelog
Log:
Add missing semi-colon to fix compilation error

Modified: trunk/src/echangelog/echangelog
===================================================================
--- trunk/src/echangelog/echangelog	2008-03-14 03:21:03 UTC (rev 481)
+++ trunk/src/echangelog/echangelog	2008-03-14 14:26:53 UTC (rev 482)
@@ -391,8 +391,7 @@
 # If there are any long lines, then wrap the input at $columns chars
 # (leaving 2 chars on left, one char on right, after adding indentation below).
 $input =~ s/^\s*(.*?)\s*\z/$1/s;  # trim whitespace
-$input = Text::Wrap::fill('', '', $input) if ($input =~ /^.{80}/m);
-$input =~ s/^/  /gm;        # add indentation
+$input = Text::Wrap::fill('  ', '  ', $input);
 
 # Prepend the user info to the input
 unless ($user = $ENV{'ECHANGELOG_USER'}) {

-- 
gentoo-commits@g.o mailing list


Navigation:
Lists: gentoo-commits: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
gentoo-x86 commit in app-office/qtstalker: qtstalker-0.32.ebuild ChangeLog qtstalker-0.33.ebuild
Next by thread:
gentoo commit in xml/htdocs/doc/pl/handbook: hb-install-network.xml
Previous by date:
gentoo-x86 commit in app-office/qtstalker: qtstalker-0.32.ebuild ChangeLog qtstalker-0.33.ebuild
Next by date:
gentoo commit in xml/htdocs/doc/pl/handbook: hb-install-network.xml


Updated May 16, 2012

Summary: Archive of the gentoo-commits mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.