[Paraview-developers] CVS->Git Transition Plan

[Biddiscombe, John A.]

Brad et al

I'm sitting on a very large number of local diffs in my CVS tree.

is there a git id/tag that I can use as a reference to pull from (for VTK/ParaView), apply my patches and then gradually work my way back to the head. I'm not very skilled at git yet. I have trouble getting somethings to work and it takes me about 10 attempts usually to work out patches and diffs between things. If there are any tips on how to manage the large transistion, please tell.

Also, for commits, who do I send my public key to?

JB



> -----Original Message-----
> From: paraview-developers-bounces at paraview.org [mailto:paraview-developers-
> bounces at paraview.org] On Behalf Of Brad King
> Sent: 19 April 2010 16:55
> To: VTK Developers
> Cc: ParaView Developers; vtk; ParaView
> Subject: Re: [Paraview-developers] CVS->Git Transition Plan
> 
> Brad King wrote:
> > CVS commits to these repositories have been disabled.  I will complete
> > the final conversions of history today and over the weekend.
> 
> We're pleased to announce the completion of the repository conversion.
> The CVS repositories have been permanently frozen (though I'll be adding
> one extra commit to them to point folks that try them at the new repos).
> 
> Development of VTK, ParaView, IceT, and Xdmf is now officially hosted
> by Git.  All repositories may be browsed online via gitweb:
> 
>   http://vtk.org/gitweb
>   http://paraview.org/gitweb
> 
> The individual gitweb pages show the repository URLs.
> The git clone/fetch URLs for the repositories are:
> 
>   git://vtk.org/VTK.git
>   git://vtk.org/VTKData.git
>   git://paraview.org/ParaView.git
>   git://paraview.org/ParaViewData.git
>   git://public.kitware.com/IceT.git
>   git://public.kitware.com/Xdmf.git
> 
> Replace "git://" with "http://" to get http protocol access.
> 
> >   http://www.vtk.org/Wiki/VTK/Git
> >   http://www.paraview.org/Wiki/ParaView/Git
> 
> The Wiki pages have been updated to refer to the official repositories.
> Additional documentation about branches, submodules, workflow, update
> hooks (previously known as commit checks in CVS) will be added in the
> coming weeks.
> 
> IMPORTANT NOTE: The official histories now published at the above
> URLs are *incompatible* with all previous Git repositories for these
> projects.  You *must* do a *fresh* clone from scratch.  Please do not
> try to pull into an existing clone that was created from the CVS->Git
> tracking repositories or any experimental repository previously
> published (even at the above URLs from any date before 2010-04-19).
> 
> In order to reduce confusion we've deleted the Github and Gitorious
> repositories that previously published the CVS->Git tracking repos.
> Furthermore, the new repositories will not yet accept merge commits.
> Please rebase your work on master before pushing to them.  We will
> switch to a branchy workflow once things have settled.
> 
> -Brad
> 
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers