On Fri, May 03, 2013 at 08:17:12PM +0400, Nikita Churaev wrote: > > list about what you intent to do the most likel outcome is lot of > > patches rotting somewhere in a corner of github. > > I'm not gonna magically pull your set of patches. > > I will review patches if they are sent on this list with explanation of > > what they are doing. And before rolling dozen of those get feedback on > > the first ones. > > I originally planned to format a patch with git from my first commit to > last when I get something finished and file it to Bugzilla (or should I > file it here to the list?), with proper explanation. > > Actually I'm going to scrap the branch and start anew, without moving > the functions around.
What do you want to achieve ? I think I understand but it is better if stated. Then we can see how to get there with minimal disruption and a clear set of patch each doing one step. Probably don't need to scrap everything, but reorganize in an easy to follow/review set. The key point is the absolute imperative of keeping API and ABI stability. I would also prefer to not add too many new entry points for both human and technical reasons (first because the API is confusingly too big already, and second because the resolution of all entry points in ELF shared library may turn quadratic and we are already quite big) Beside that I will hadly say no to anything improving documentation :-) thanks ! Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veill...@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/ _______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml@gnome.org https://mail.gnome.org/mailman/listinfo/xml
