Just to check, is the plan to take JCS out of Turbine in CVS, or to
move to SVN and then move it?

Hen

On Tue, 4 Jan 2005 09:02:03 -0500, Henri Yandell <[EMAIL PROTECTED]> wrote:
> Why not migrate them to SVN as well?
> 
> That way there'll be a source repository history of their move.
> 
> Hen
> 
> On Tue, 4 Jan 2005 10:10:17 +0000 (UTC), Henning P. Schmiedehausen
> <[EMAIL PROTECTED]> wrote:
> > Henri Yandell <[EMAIL PROTECTED]> writes:
> >
> > >Specifically to Daniel and Henning.
> >
> > >Any update on the plans for the SVN migration? I'm pretty sure it was
> > >originally suggested that it would be after JCS was promoted? If so,
> > >wouldn't a promotion be easier to do in SVN than CVS?
> >
> > >Just hassling you along basically :)
> >
> > Hi,
> >
> > I don't know when the JCS guys get their act together. I pinged Aaron
> > a few times and he said "yes, I'll do it" (I know, I say this
> > sometimes, too).
> >
> > Our migration to SVN shouldn't be stopped by JCS. They will simply
> > stay in CVS and we move on. We have a plan on how to migrate worked
> > out and I am able to wield cvs2svn. Basically, I just need a few
> > continuous free cycles.
> >
> >         Regards
> >                 Henning
> >
> > --
> > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
> > [EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/
> >
> > RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
> >    Linux, Java, perl, Solaris -- Consulting, Training, Development
> >
> > What is more important to you...
> >    [ ] Product Security
> > or [ ] Quality of Sales and Marketing Support
> >               -- actual question from a Microsoft customer survey
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to