On Wed, 2006-12-06 at 22:28 +0100, Patrick Bernaud wrote: > Hi all, > > Ales Hvezda writes: > > [...] > > The question becomes, when do we want to merge it. I would say > > let's merge it as soon as possible and then deal with any issues on > > a case by case bases. > > I would like to try an alternative to Carlos 'zoom while moving' > changes of the branch (not the ones for 'GList as selection'). In fact > I was hopeful that I could have provided some kind of a preview source > tree for today meeting but I did not succeed. > > So I would rather have this merge postponed for a few days at least. > > Regards, > > > Patrick
Is it possible for the branch to be sync'd up with changes on head, in preparation for a merge? I'm trying to keep my noscreen changes in sync with glist-dev, which is its self currently out of sync with head. Also, Patrick... when you have your preview source code, could you send a diff against glist-dev (or wherever you based it), as I'd be interested to see how it would adapt with the noscreen changes. Since glist-dev has been stable, and scheduled for merging for some time now, it seemed like starting noscreen changes based upon it wouldn't create too large a burden at merge time. Perhaps if your code isn't ready yet, you might describe how it is different to Carlos's work? If anyone wants to see the noscreen changes, I will try and publish it somehow. (gitweb if I can find somewhere to host it). It is all in GIT at the moment, even if the initial changes were in one fairly atomic commit across the code base (when I switched to GIT). Most of my effort now is in tidying up the individual later commits, and perhaps merging some (fixes) back into the initial patches. I'm investigating stgit for managing this as a nice series of patches. Regards Peter Clifton _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
