[cmake-developers] Topic branches in limbo on the stage?

David Cole david.cole at kitware.com
Wed Feb 8 16:08:07 EST 2012


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
                                               qt4-deploy | master=0 next=0
                    HandleTargetsInCMakeRequiredLibraries | master=0 next=0
                     CPackNSIS-fixIgnore-INCLUDE_TOPLEVEL | master=0 next=0
                                          qt4-deploy-test | master=0 next=0
                                            findblas-bugs | master=0 next=0

If it's ready to be tested on the dashboard machines, then please merge it
to 'next'.

If not, and you are the developer responsible for one of these (author,
committer, reviewer) please coordinate with whomever you need to in order
to get these things into 'next' soon. The 'cc' line here are authors and
committers of the tips of these branches.

Or... if you've abandoned the work, or you do not have time or do not plan
to work on this within the next two weeks, please just grab a local copy,
and then delete the topic from the stage:

  git fetch stage
  git checkout -b topicname stage/topicname
  git push stage :topicname

(Of course, replacing "topicname" with the actual name of the topic you are
deleting.)

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.

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.
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.


Thanks,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120208/103483b6/attachment-0001.html>


More information about the cmake-developers mailing list