Hi Frank! Frank Naumann wrote:
Hello!I also thought that not all of the changes projects hosted in the FreeMiNT cvs directly should be sent to FreeMiNT's mailing list.Yes, we can limit the commit sending to freemint, mintlib, lib and create maybe another mailing list for the rest (for example). What's the opinion of the other subscribers of the freemint cvs commit mailing list?
That would work too.
I thought about even more radical solution... It is not a problem to move those projects out of scope of the FreeMiNT cvs and have them each inside a separate repository, right? Then you gain more control in regard to repository write access and such. But also some more work to maintain multiple repositories.Yes, this is possible. But I don't see much benefits yet. We are not so much developers, most of us know each other :-) So I don't think access control is a problem.
Right.
Your initial question with QED cvs was whether there should be a new repository for that. I should have probably said that it is not mint related and therefore it should go to a separate module.You mean the QED module should be in a separate repository?
Well, I don't care that much, but in case we do any project CVS repository separation it should go to separate one then. No need to change this if the maling list split would work for us here...
Best Regards STanda