Don't look at the metacello version numbers�� versions are maintained by git ��--- so I can have the same version number refering to different code in different branches. (There's no clash because one branch will never know about another one.)

The important is what is fetched from github:

Fetched -> BaselineOfBar-PeterUhnak.11 --- github://peteruhnak/ci-bar:cycle/repository [6ac72c0:cycle] --- github://peteruhnak/ci-bar:cycle/repository

Fetched -> BaselineOfBar-PeterUhnak.11 --- github://peteruhnak/ci-bar:deps/repository [03d743b:deps] --- github://peteruhnak/ci-bar:deps/repository

On Tue, Feb 16, 2016 at 11:17 AM, Werner Kassens <wkassens@libello.com> wrote:

Hi Peter,
in your second example, which has a new BaselineOfZar & of bar, BaselineOfZar-PeterUhnak.9 & BaselineOfBar-PeterUhnak.11 is fetched, which have the same versionnumber as in the 1st example, are you sure, that the new baselines of ex2 are loaded?
werner

On 02/16/2016 09:33 AM, Peter Uhn��k wrote:

Unfortunately #includes: doesn't seem to matter and I still get errors.

I tried to somehow summarize my findings with minimal code & results
here http://peteruhnak.com/metacello/