[Python-Dev] hg diff
Antoine Pitrou
solipsis at pitrou.net
Mon Mar 7 18:31:12 CET 2011
More information about the Python-Dev mailing list
Mon Mar 7 18:31:12 CET 2011
- Previous message: [Python-Dev] hg diff
- Next message: [Python-Dev] hg diff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 7 Mar 2011 12:04:18 -0500 Barry Warsaw <barry at python.org> wrote: > On Mar 07, 2011, at 11:44 AM, Tres Seaver wrote: > > >If we can get to a mode where non-committers can push to a "fork" on > >hg.python.org, we can dodge the patch format issue by having folks post > >"pull requests" for that fork instaed. > > > >For the repoze and pylons projects, we have found the quality and > >quantity of patches went up *significantly* when we made it easy for > >somebody who doesn't work on the code all the time to use this workflow > >(fork to a public repo, clone, hack, commit, push, request a pull). > > +1. 'Branches' are better than patches. How do you review a branch?
- Previous message: [Python-Dev] hg diff
- Next message: [Python-Dev] hg diff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list