Re: [Python-markdown-discuss] Ticket #000057

[Waylan L. <wa...@gm...>]

On Thu, Mar 18, 2010 at 11:00 PM, Gerry LaMontagne
<gjl...@al...> wrote:
>
> Alright, I've got 2 different possible fixes for you to evaluate.

Thanks. I've committed your patch2.diff as it more closely follows the
existing pattern in the parser.

> I haven't had a chance to dig into the other item I noted previous, but
> it's on my todo list.

Cool. A few things :

I've created Ticket 58 [1] to track that issue.

If you create an account and clone [2] at gitourious.org, you can push
your commits up, and make merge requests [3].  Then I can merge your
commits and you will get full credit in the log as the commiter (not
just via my comments). Of course, if you'd rather not, that's fine
too.

Could you continue any further discussions on the mailing list [4] so
others can pitch in if they want and so that we have an archive of how
the solution was reached (I'v copied the list with this response.
Probably should have done this earlier).

Your time and energy on this is **very much** appreciated. I've barely
had the time to review and commit your patches.  There's no way I
would have had the time to debug the problems and hack the patches
together myself.

[1]: http://www.freewisdom.org/projects/python-markdown/Tickets/000058
[2]: http://gitorious.org/python-markdown/mainline/clone
[3]: http://gitorious.org/python-markdown/mainline/merge_requests
[4]: https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss

--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg