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.


>
> 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".

-Pete
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to