Hi JT, On Thu, Feb 02, 2012 at 10:47:24AM -0700, JT Olds wrote: > Alright, that sounds good. I can't figure out how to attach a patch to > http://www.logilab.org/ticket/88218, so it's attached to this email.
It is a single short patch, attaching it to your email is fine. Ideally, you would have found http://www.logilab.org/repository/60962 and done a `hg clone http://hg.logilab.org/patches/pylint` then put a patch in there (with mercurial's mq extension) and publish that repository somewhere else for us to pull from. When your patch gets pulled, it enters the review system and shows up in http://www.logilab.org/project/pylint?tab=vcreview_patches_tab If you have an account on bitbucket, it is even simpler. Just fork https://bitbucket.org/nchauvat/pylint-patches/ and send your pull request by email to the mailing list. FWIW, We are working on improving this and making simply the distributed review process with mercurial, but it takes time. An important milestone was reached this week with the release of Mercurial 2.1 and the Phases feature: http://selenic.com/pipermail/mercurial/2012-February/041644.html Stay tuned ! :) -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
