Re: [cmake-developers] Topic branches in limbo on the stage?
On Wednesday 08 February 2012, David Cole wrote: The stage is intended only for topics that are imminently going to be merged to 'next'... The following CMake topic branches have been on the stage for quite some time without being merged to 'next': UseEnabledLanguagesForDirectoryInformationFileIncludePath | master=0 next=0 I forgot to delete that one, done. qt4-deploy | master=0 next=0 HandleTargetsInCMakeRequiredLibraries | master=0 next=0 I will continue to work on this one in the next days. CPackNSIS-fixIgnore-INCLUDE_TOPLEVEL | master=0 next=0 qt4-deploy-test | master=0 next=0 findblas-bugs | master=0 next=0 Alex -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Topic branches in limbo on the stage?
2012/2/8 David Cole david.c...@kitware.com: The stage is intended only for topics that are imminently going to be merged to 'next'... The following CMake topic branches have been on the stage for quite some time without being merged to 'next': CPackNSIS-fixIgnore-INCLUDE_TOPLEVEL | master=0 next=0 If it's ready to be tested on the dashboard machines, then please merge it to 'next'. Just done for this one which is mine. It fixes bug #12935. Now for have been on the stage for quite some time You guys will be reaching light speed soon enough; You mail: 2012/2/8 David Cole david.c...@kitware.com: My unmerged commit: commit 6a74eb1d36b079fe6b566244a636ac1e43303aa6 Author: Eric NOULARD eric.noul...@gmail.com Date: Sun Feb 5 13:13:48 2012 +0100 3 days!! Just kidding but... Thanks -- that will make our weekly merge sessions easier to do when we don't have to deal with this handful of noise that's not ready yet. OK. Please consider using github or some other free online git hosting facility for sharing branches with others when they are not yet ready for next. Noted too. Eventually, we'll get a gerrit instance to host CMake for us so that we can review changes in gerrit and avoid this sort of thing by default. Would be nice. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
