[Paraview] Git or CVS for ParaView 3-8 Code

[Dave Partyka]

The official way is to use cvs until the transition occurs. I am using cvs
for building the 3.8 release binaries because cvsexport is just another
level of complexity I don't want to deal with, especially for merging fixes
onto the branch. I am not certain why GitHub didn't import the entire branch
but it is going to be disabled soon anyway.

On Tue, Apr 6, 2010 at 10:45 AM, Michael Jackson <
mike.jackson at bluequartz.net> wrote:

> I would like to work with the ParaView 3.8 branch. What is the "official"
> way to get the code? Git or CVS? The Git server at GitHub seems NOT to have
> all the source code for the branch. Is the CVS server still active?
>
> Thanks
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
> Principal Software Engineer       mike.jackson at bluequartz.net
> BlueQuartz Software               Dayton, Ohio
>
>
> _______________________________________________
> 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 ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100406/3900b60b/attachment.htm>