{"thread":{"id":"17045","subject":"Git for Product Line Engineering","startedAt":"2009-01-08T09:01:46Z","lastAt":"2009-01-08T09:01:46Z","messageCount":1,"participants":["Michail Anastasopoulos"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"99685","messageId":"loom.20090108T085342-994@post.gmane.org","threadId":"17045","inReplyTo":null,"subject":"Git for Product Line Engineering","fromName":"Michail Anastasopoulos","fromEmail":"manast@gmx.de","sentAt":"2009-01-08T09:01:46Z","receivedAt":"2009-01-08T09:01:46Z","isPatch":false,"sender":{"key":"manast@gmx.de","avatar":null},"body":"Hello,\nI was wondering if anyone of you has applied git to manage the evolution of a\nproduct line. In such a context management of software reuse and permanent\nvariation becomes necessary.\n\nI think that the distributed character of git as well the easier handling of\nbranches could be very beneficial in such a context.\n\nYet I was wondering how the relations between reusable and reused things could\nbe managed?\n\nIf for example I am the maintainer of a library in a product line context I want\nto know who pulls from me and whether my library had to undergo any\nproduct-specific changes in any of the other repositories that belong to my\nproduct line.\n\nRegards,\nMichalis\n"}]}