{"thread":{"id":"16055","subject":"[ANNOUNCE] intergit repository-linking tool (early release)","startedAt":"2008-10-27T02:22:37Z","lastAt":"2008-10-27T02:22:37Z","messageCount":1,"participants":["Christian Jaeger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"94013","messageId":"490525ED.8080702@pflanze.mine.nu","threadId":"16055","inReplyTo":null,"subject":"[ANNOUNCE] intergit repository-linking tool (early release)","fromName":"Christian Jaeger","fromEmail":"christian@pflanze.mine.nu","sentAt":"2008-10-27T02:22:37Z","receivedAt":"2008-10-27T02:22:37Z","isPatch":false,"sender":{"key":"christian@pflanze.mine.nu","avatar":null},"body":"Hello\n\nTen days ago I started a thread about \"Separating generated files?\" [1], \nand suggested in the end that instead of using git submodule \nfunctionality, one might be better off using a tool which can, upon \ncommitting files in the repository containing generated files, add a \nlink (\"reference\") pointing to the commit in the source repository which \nrepresents the source files they have been generated from, and then when \nsomeone is checking out some revision of the source files later, use \nthis information to find the (best-)matching commit in the repository \nwith the generated files. This may also be useful in other situations \nwhere one likes to keep repositories separate but they have a version \ndependency on each other.\n\nI've now written a first version of a pair of these two programs, which \naccomplishes this. You can get them from:\n\nhttp://www.christianjaeger.ch/dyn/pubgit/gitweb?p=intergit.git;a=summary\ngit clone http://christianjaeger.ch/pubgit/intergit.git\n\nThis will need some finish before really being production ready; it will \nmainly need some experimentation on how it is to be used exactly, so \nthat possibly missing features in the search and indexing algorithms can \nbe added (like whether it should understand merges between two commits \ncontaining references as a commit having both references even if the \nmerge commit doesn't specify a reference), and I'm also keen on some \nfeedback implementation-wise (building the index is currently slow, and \nsome of the problems that I'm listing in the docs (Implementation.txt \nand TODO.txt) may have solutions I've not been aware of). I've tried to \nadd some useful documentation (see *.txt files), so I'm hoping this \nhelps anyone interested to understand how it works, or just give me some \nfeedback on how it may or may not be useful.\n\nI've developed and tested it on Linux. Hints on whether it works under \nother systems and how to make it work with msysgit would be very \nappreciated.\n\nChristian\n\n[1] http://marc.info/?l=git&m=122415845625044&w=2\n\nPS. I've just noticed the thread about \"repo - The Multiple Git \nRepository Tool\". I'll have to take a look first to see how it is \nrelated to my program--it may take me a few days as I'll be busy.\n\n--\nMy OpenPGP fingerprint: F033 D030 F75D E445 05A1  1865 4ECB DF80 1FE6 92DA\n"}]}