fenics team mailing list archive

[Andy Ray Terrel <andy.terrel@xxxxxxxxx>]

Person A and Person B fork from repo O (for original).

On Github A can put a pull request to B, but not bitbucket.

Okay so you can just email the patch, but you don't get the super
nifty code review interface.

-- Andy

On Tue, Mar 19, 2013 at 1:12 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> What does that mean? A pull request from two separate branches?
>
> --
> Anders
>
>
> On Tue, Mar 19, 2013 at 09:48:22AM -0500, Andy Ray Terrel wrote:
>> I have been playing around with the branches on bitbucket and I have
>> to say I'm less impressed.  With github, we would just give
>> instructions for each individual to fork the
>> github.com/fenics/package.git repo and push their branches to their
>> space.  Then a pull request (or merge request) can be done in the same
>> fashion as lp. The show up as issues and can be referenced easily plus
>> they have a nice listing.  We can also setup a buildbot for the pull
>> requests that show if pull request pass the tests, for example see
>> https://github.com/sympy/sympy-bot .
>> On Bitbucket I haven't figured out how to do a pull request from two
>> separate branches (only to the main repo and its forks).  Jed tells me
>> to send a bug report,
>> -- Andy
>
>
>
>>> A third practical issue, we need to think about how we cleanly transition
>>> branches.
>>>
>>> David
>>>
>>>
>>>
>>>
>>>
>>>
>>> http://www.imperial.ac.uk/people/david.ham
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~fenics
>>> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fenics
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~fenics
>> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fenics
>> More help   : https://help.launchpad.net/ListHelp