Last modified: 2011-09-05 20:15:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 30767 - perltidy [PATCH]
perltidy [PATCH]
Product: MediaWiki extensions
Classification: Unclassified
EasyTimeline (Other open bugs)
All All
: Unprioritized trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch
Depends on:
  Show dependency treegraph
Reported: 2011-09-05 17:28 UTC by Amir E. Aharoni
Modified: 2011-09-05 20:15 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

the complete file to which run through the perltidy script (169.77 KB, application/x-perl)
2011-09-05 17:28 UTC, Amir E. Aharoni

Description Amir E. Aharoni 2011-09-05 17:28:39 UTC
Created attachment 9015 [details]
the complete file to which run through the perltidy script

I am hacking on Bug 4030. I spoke to Erik Zachte about it in Haifa, and he said that since i know Perl and he doesn't have time to maintain this extension, i can do more or less anything i like with it (Erik, correct me if i'm wrong :)

It will be much easier for me to edit this code if it would be updated according to the common Perl coding standards.

The diff is very big, but this version doesn't change any functionality. It only tidies the whitespace using the automatic program perltidy ( ). I tested it on my MW installation and it still creates proper timeline images.
Comment 1 Niklas Laxström 2011-09-05 20:15:15 UTC
Applied in r96294.

Note You need to log in before you can comment on or make changes to this bug.