help getting a clue about tracking changes in an integrated library

[Marius Kruger]

On 23 September 2010 06:39, Chris Hecker <checker at d6.com> wrote:
>
>> This is exactly the "poor man's nested branch" model. Since you've
>> invented it for yourself, it's the obvious way for you to go.
>
> No, I think this is different.  I'm proposing this:
>
> repo1 - trunk -+- src
>               |
>               +- lib
>
> repo2 -+- lib-mine
>       |
>       +- lib-mod
>       |
>       +- lib-orig

You may also be able to use one of the following to help you manage
these branches:
https://launchpad.net/bzr-externals
https://launchpad.net/bzr-scmproj

I've used both in anger and they help a lot.
(I haven't read this thread in detail, so I may have missed some
reason why you don't want these solutions)

-- 
<>< Marius ><>