anonym wrote (01 Aug 2013 10:24:22 GMT) :
>> I'm not sure how we should handle that in the general case (and am
>> more and more tempted to put all that stuff into Git submodules of our
>> main repo),
> Submodules sounds like a good idea, but is it really there the problem
> is?
> Or perhaps it will help reminding us to use the review'n'merge since
> those code bases are moved into one we're used to review'n'merge for
> every change.
That's what I meant, yes. On a technical level, it would force us to
explicitly merge version Y of software X into the Tails main repo
(devel or whatever branch). Given we have good ways to handle merges
into these branches already, I guess we could easily get used go
through the same (now usual) review'n'merge process.
Cheers!
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
