merging of trunk to fortran-dev?

[Tobias Burnus]

Janus Weil wrote:
>> The old fortran-experiments branch was/is severely messed-up.
>> It may be painful to bring it up to date.
>>     
> Ok, I didn't know that. I proposed this because I thought it would be easy.
>
> Also I won't oppose the fortran-dev plan if all other alternatives
> turn out to be more inconvenient.
>   

Creating a new branch is simple (just do it and add it to the list of
branches at http://gcc.gnu.org/svn.html).

The question is just what is more convenient:
a) A shared development branch
b) Having several, separate development branches

(a) has the advantage that it is easier to test a single additional
branch than several branches. (b) has the advantage that merging to the
trunk is easier. If the patches are orthogonal, i.e. they touch separate
places (better: different files, best: different directories), I would
go for a single branch for both. Otherwise, I would suggest to create
another branch.

Tobias

PS: BTW - newer svnmerge.py scripts call now "svn merge".

PPS: I have just updated fortran-dev to the branch: 155317-155509 (as
Rev. 155511).

PPPS: At some point I would like to start developing Coarrays on a
branch - at least if others are also interested working on it. Otherwise
having the changes locally such that a "svn up" is enough to update to
the latest trunk is simpler.