Hi, On Sat, Aug 13, 2011 at 03:55:32AM +0200, Gelonida N wrote: > In a few simple sentences: > The doc does not mention > ...
You chose the option "report to the list" which is more work on our side than one of the options based on sending a patch, but thank you for your input, we'll use it as soon as possible. > > - or even better clone http://hg.logilab.org/patches/pylint/, commit your > > patch into that repo, make the repo available online and send us a > > pull request with your report. > > Well perhaps it's a nice excuse to make first tests with hg. So far I > used only git. http://mercurial.selenic.com/wiki/GitConcepts#Command_equivalence_table http://hg-git.github.com/ > Is there anything like github for hg? > Oherwise I had difficulties to make the repo available online. https://bitbucket.org/ > Of course one can google for it, but perhaps this might reduce the > 'barrier' for contributors not knowing hg. > A short l document explaining the minimalist flow of > how to checkout the repository (found it in the section source code of > the pylint web site) > how to fix, > how to commit, > how render public a repo > and perhaps one link to a more complete hg doc. http://mercurial.selenic.com/quickstart/ http://mercurial.selenic.com/wiki/Tutorial http://hginit.com/ -- 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
