Hello again, As I said in my previous mail, I'm using a common monotone repository to group all the projects I follow. As the options for the repo are mostly common for all the synced projects, there's a lot of duplicated options:
[monotone:projectA] module = net.example.projectA repository = myrepo.mtn keyid = [EMAIL PROTECTED] passphrase = lala [monotone:projectB] module = net.example.projectB repository = myrepo.mtn keyid = [EMAIL PROTECTED] passphrase = lala I propose some kind of subclassing for the repository sections, with something like this: [monotone:common] repository = myrepo.mtn keyid = [EMAIL PROTECTED] passphrase = lala [monotone:projectA] base = common module = net.example.projectA [monotone:projectB] base = common module = net.example.projectB or even: [monotone:common:projectA] module = net.example.projectA [monotone:common:projectB] module = net.example.projectB I suppose it would be also helpful for other situations. What do you think about it? Thanks for your work! Regards, Jordi Vilalta _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
