[Python-Dev] Long term development external named branches and periodic merges from python
Nick Coghlan
ncoghlan at gmail.com
Thu Nov 24 23:46:23 CET 2011
More information about the Python-Dev mailing list
Thu Nov 24 23:46:23 CET 2011
- Previous message: [Python-Dev] Long term development external named branches and periodic merges from python
- Next message: [Python-Dev] Long term development external named branches and periodic merges from python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Nov 25, 2011 at 7:46 AM, Xavier Morel <python-dev at masklinn.net> wrote: > On 2011-11-24, at 21:55 , Nick Coghlan wrote: >> I've never been able to get the Create Patch button to work reliably with >> my BitBucket repo, so I still just run "hg diff -r default" locally and >> upload the patch directly. > Wouldn't it be simpler to just use MQ and upload the patch(es) from the series? Would be easier to keep in sync with the development tip too. >From my (admittedly limited) experience, using MQ means I can only effectively collaborate with other people also using MQ (e.g. the Roundup integration doesn't work if the only thing that is published on BitBucket is a patch queue). I'll stick with named branches until MQ becomes a builtin Hg feature that better integrates with other tools. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Long term development external named branches and periodic merges from python
- Next message: [Python-Dev] Long term development external named branches and periodic merges from python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list