On Wed, 2012-02-29 at 10:11 +0100, Jonas Bonn wrote: > On Wed, 2012-02-29 at 08:47 +0000, Jeremy Bennett wrote: > > On Wed, 2012-02-29 at 09:01 +0100, Jonas Bonn wrote:
> > We have had this discussion in the past, and agreed that we would use > > SVN where the upstream uses SVN or CVS and git where the upstream uses > > git. > > That was years ago... cans of worms are meant for opening. Old > arguments don't necessarily apply anymore. We all met in late June 2011, and the discussion continued after on the mailing lists. That is 8 months ago. > > Sticking to the one true repository solves this. That is why I have > > proposed Pete should have SVN write access to commit his code. Since he > > is mirroring mainline, he is familiar with SVN and CVS anyway. > > Mainline publish git repositories, no mirroring skills required... GCC is mastered in SVN, all the other components (binutils, GDB, newlib) in CVS. They both maintain read-only git mirrors. If we are serious about committing upstream, we need to be working in the upstream version control system. > > The current tool chain went through extensive testing to ensure it is > > robust. I am delighted that someone is taking that work forward, and > > congratulations to Pete for his contribution. > > Two years ago... and since then? And yes, congratulations to Pete for > his contribution... Embecosm put in a major contribution to the tool chain in the months up to June 2011, 8 months ago. Since then I have made a number of bug fixes. > > But we need to follow our agreed engineering process, ensure the new > > code is tested to the same standards as the old, reviewing on these > > mailing lists. It will initially be the development version of the tool > > chain, and then later will become the stable version. > > > Why do you refuse to push upstream when it's tested and working? Now > we're two years behind again and essentially back to square one in terms > of needing to catch up. We need copyright assignment to the FSF. That needs all those who have contributed to the tool chain since 1999 to assign their copyright. It is not an impossible task, but there are a large number of people to be contacted. Linux is much easier - no requirement for copyright assignment. That does not mean we should not track upstream in preparation. Falling behind is a measure of the effort that has been available to the project, not a failure to commit upstream. Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Email: [email protected] Web: www.embecosm.com _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
