It is always difficult for users to track changes between larger patches. I think Johannes did it right with his css-prototype repository. It is not the best thing to directly integrate bigger patches into mainline as they might be yet incomplete or lead to instabilities. Thus, having additional repositories is a good thing. If the features are stable enough and are thought to be useful, they can be simply merged into the main tree. In the Git world, where nearly everything is decentralized, it frequently happens that every core developer has an own repository for experimental changes. Of course this approach might not be always practical for smaller projects but we all can benefit from the fundamental idea of decentralisation. For Dillo, experimental per-feature repositories would be very useful before not well-tested patches go into mainline and risk the application's stability. Hence, I advocate that we make use of external repositories more frequently assuming it makes sense based on the changes' size. --Tim