Skip to content
Commits on Feb 7, 2016
  1. Update copyright for 2016.

    committed Feb 7, 2016
Commits on Feb 6, 2016
  1. Update changelog. [ci skip]

    committed Feb 6, 2016
Commits on Feb 2, 2016
Commits on Jan 11, 2016
Commits on Dec 16, 2015
  1. Add note on caveats [ci skip]

    committed Dec 16, 2015
Commits on Dec 5, 2015
Commits on Nov 2, 2015
  1. Fix appveyor release bug (#126)

    committed Nov 2, 2015
  2. Version bump for 0.5 [ci skip]

    committed Nov 2, 2015
Commits on Oct 29, 2015
  1. release/0.4.3

    committed Oct 29, 2015
  2. Tweak for clarity (#126)

    committed Oct 29, 2015
  3. Typo.

    committed Oct 29, 2015
  4. Try another approach (#126)

    committed Oct 29, 2015
  5. Fix typos.

    committed Oct 28, 2015
  6. Debugging stuff for Windows.

    committed Oct 28, 2015
  7. Fix Python version parsing.

    committed Oct 28, 2015
  8. Windows fix (#126)

    committed Oct 28, 2015
Commits on Oct 16, 2015
  1. Add Python 3.5 to Appveyor.

    committed Oct 15, 2015
Commits on Oct 3, 2015
Commits on Oct 2, 2015
  1. Add failing test cases for #125.

    committed Oct 2, 2015
Commits on Sep 23, 2015
Commits on Sep 22, 2015
  1. Travis fix for Python 3.2.

    committed Sep 22, 2015
Commits on Aug 26, 2015
  1. Merge pull request #118 from yuvipanda/cleanup

    committed Aug 26, 2015
    Remove debian/ folder out of upstream
  2. @yuvipanda

    Remove debian/ folder out of upstream

    yuvipanda committed Aug 26, 2015
    As I read more and talked to more people, I've realized that
    people were right and I should maintain the debian package
    outside of the upstream repo :) Specifically, see
    
    https://wiki.debian.org/DebianMentorsFaq#What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F
    
    The package is now maintained at github.com/yuvipanda/mwparserfromhell
    and should hopefully go into debian soon!
Commits on Aug 8, 2015
  1. Merge pull request #116 from yuvipanda/debian

    committed Aug 7, 2015
    Add debian packaging
  2. @yuvipanda
Something went wrong with that request. Please try again.