> Carlos, what's your thoughts on all this? I am still very interested > in getting your GList changes into HEAD. > > PeterC, how about you, how does this delay impact your work/patches?
Delay is no problem... I'm currently programming (24 hrs if necessary) in a mini code-sprint to get a test-suite running for an experiment (we have visitors on Thursday). Unfortunately, gschem will have to wait. I agree that Patrick's changes may be technically superior in the Undo respect, but it would be _REALLY_ nice to let people know what he's working on them first! I do feel that the goalposts have been shifted slightly here. I expect I will have to re-apply my initial monolithic patch manually re-based on the latest HEAD after Patrick's code changes, and see how much needs re-doing. A diff from Patrick would be handy to see the impact, rather than a complete tarball. (I've not had chance to get the version he based it off and run the diffs myself). I was hoping to split down my original patch, perhaps into per-file, or per-object type patches - even if they must all apply at once to build. It should also be possible for me to merge later patches into those, such as bug-fixes on top of my own work. This all requires lots of time and effort, so in the grand scheme of things, doing it on top of Patrick's changes is not much harder. I'm still not sure how much architectural change there is in Patrick's code (no time to diff etc..), so it could be "interesting", especially as it needs merging with Carlos's branch before being comparable to my code. Is Carlos's moving / rotating whilst zooming code much different from the current way of doing things? (I remember seeing abuse of the undo mechanism for this in HEAD). If not, would it be possible to apply Patrick's undo-less solution on top Carlos's branch, rather than HEAD? (Just a thought) Regards, Peter C _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
