This is 'milestones/2.0.4-beta'.
According to Dana@Ricardo email on 30/Apr/2015, he FORKed 2a006e6dacf5e7
but JRC(ankostis) assumes he meant the next-one, non-merge commit:
tag:milestone/2.0.4-beta2@ab66a68b7333cd8
Nevertheless, by searching, discovered that:
Dana was referring to folder '/vecto-sim-ricardoaea/',
imported originally on 16-Sep-2014, and left there almost untouched hereafter
(now tagged as 'auxmerge/ric-import_vecto_core_invalid1@273e72bd626b1653d97').
BUT Ricardo's code was eventually based on '/vecto-sim-ricardoaeaTB' folder,
imported for the 1st time on 30-Sept-2015,
(now tag as 'auxmerge/ric-import_vecto_core@414ea89aac15312',
and in JRC's fixup-branch as 'auxmerge/ric-import_vecto_core@87627329528baf0770'.
EVEN MORE, the cases was not just like this....
By searching tom see which was the actual fork-commit for 'TB' folder
I got these results:
$ git diff tag auxmerge/jrc_fixup-import_vecto_core milestones/2.0.4-beta2|wc
1104528 1594313 37141033
diff tag auxmerge/jrc_fixup-import_vecto_core milestones/2.0.4-beta1|wc
1104502 1594153 37139993
$ git diff tag auxmerge/jrc_fixup-import_vecto_core milestones/2.0.4-beta|wc
1104461 1593946 37138503
The less DIFFS are with '2.0.4-beta'!
So clearly this is the FORK COMMIT