On Thu, 2012-12-20 at 15:09 -0500, Peter Gavin wrote: > Hi Jeremy, > > On Thu, Dec 20, 2012 at 2:36 PM, Jeremy Bennett > <[email protected]> wrote: > For a long time, the problem with the sourceware components > (binutils, > > gdb, cgen newlib etc) has been that they have been mirrored as > individual tools, rather than as a single tree. However the > upstream > tree is in CVS, and uses CVS modules, which is why you get > multiple > copies of opcodes, bfd, include directories, even though in > the upstream > CVS they are the same. This can make it really hard to keep > changes to > these libraries in step when working in git, and can make > synchronization a nightmare. > > > I'm not sure I follow you. The tree we've been working in is a cvs > checkout of the sourceware tree, that's then been checked into git, > with all the CVS metadata included. There's only one copy of each of > those tools in this tree.
Hi Pete, Ah OK - you are doing the same as Simon is doing. I'd got into my head you were merging the various official git mirrors, and so having to decide how to deal with multiple copies of BFD etc (I know it's not that hard, just take the first one you find). We're now running GNU tool chain development for several architectures under git, so we needed a git mirror of the entire Sourceware tree. > > Fortunately this is now solved. There is a GitHub mirror of > the entire > sourceware CVS tree, updated every 3 hours: > > git://github.com/embecosm/sourceware.git > > Hopefully this should make synchronization with upstream much > easier in > the future. Thanks to Simon Cook who set this up. > > > We'd have to port all of our changes over to this tree. That > shouldn't be difficult, I suppose. But updating the current tree is > as easy as doing "cvs update" followed by "git merge". If your current flow is working there's no reason to change. The mirror is there if it is helpful in the future. Best wishes, 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
