Hello! > - RP: important not to let backwards compatibility stand in the way of > progress; development tree needs to move forwards. There will come a > point where old stuff cannot be sensibly maintained and must be deleted: > e.g. old gcc versions do not support sysroot which is needed for staging > nowadays. > > - Phil B: agreed, but would prefer to keep old versions working as long > as there is little/no cost in doing so. > > - KG: lots of old cruft in tree makes it hard for new users to find > examples of best current practice. > > - Phil B: can we move the cruft out of sight rather than deleting it? > Punt this to discussion on splitting the tree.
I just want to remind about tagging possibility of git :) We can (and imho definitely must) tag revisions before dropping any of such things. -- Yuri Bushmelev _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
