fenics team mailing list archive

[David Ham <David.Ham@xxxxxxxxxxxxxx>]

As a different issue,  we have a fairly persistent ffc branch which is
unlikely to be merged on the timescales we're talking about here, so
if there is a clean way for us to end up with a branch of the new
trunk which has our ffc branch (preferably with its history), that
would help. I imagine we're not the only people sitting on branches we
don't want to die.

David

On 6 February 2013 15:43, Martin Sandve Alnæs <martinal@xxxxxxxxx> wrote:
> Whether to merge all fenics projects into one repository was discussed
> offline in january, my tests of today show that it is definitely feasible.
>
> Before we eventually do that, we should allow some time for people to
> foresee eventual issues, e.g. we'll need changes to the buildbot, which
> projects should be included, etc.
>
> The blueprint interface is not really a good place to discuss, as it doesn't
> handle concurrent access by multiple users, so chip in on this thread if you
> have anything to say.
>
> Here's a summary of pros and cons:
> https://blueprints.launchpad.net/fenics/+spec/combine-projects-into-one-repository
> including a link to an already merged repository prototype and a script to
> create it.
>
> Martin



-- 
Dr David Ham
Department of Computing
Imperial College London

http://www.imperial.ac.uk/people/david.ham