> 2013/7/21 Kai Tietz: > > Hi > > > > as far as I remember we discussed that we shouldn't touch first hand old > > structure. First building up new tree and then move *unnecessary* parts > > away, or/and at least announce changes in front with community to avoid such > > fallouts. It is worse to have some changes/temporary fallouts. > > Nevertheless we have to inform before changing way of access. > > Hmm... > Ok. > > -- > Regards, > niXman
niXman, Perhaps you are planning a followup email to this thread that summarizes the next steps, the expected directory structure, the timeline, etc. If so, after you, Kai, and JonY have sync'd up again on the details, I'd be happy to proofread the email before you send it out. Since English is not the mother language of all members of this ML, as a native English speaker I might be able to help make the followup email a bit more clear. Actually, I'd volunteer Erik van Pienbroek to review (his style is both informative and readable) but I don't know him well enough to try to stick him with this one ;) Bottom line: if you'd like another set of eyes to review for English and clarity, I'd be more than happy to assist. Just email me a version off-list. If not, that's fine and I'm looking forward to the new `mingw-w64-builds` directory contents of "official" builds :) Jon --- Fail fast. Fail often. Fail publicly. Learn. Adapt. Repeat. http://jonforums.github.io/ | http://thecodeshop.github.io/ twitter: @jonforums ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
