The 'clone and own' approach to software product lines assumes that
variants are created by cloning and evolve more or less
independently afterwards. In this paper, we describe a process to
manage similarity of such 'cloned and owned' variants along the
timeline. The process uses annotations for recording developer
intentions and it leverages automatic change propagation. We
describe a case study where we manage similarity for
clowned-and-owned Haskell-based variants of a simple human-resources
management system.