I can do it but my time is very limited. So if you can find someone to push
it from cvs to svn you'll get there much sooner than if you left it in my
hands.

Mark

On 7/25/07, Andrew Petro <[EMAIL PROTECTED]> wrote:
>
>  Mark,
>
> Ok.  Is committing this code into SVN something you're comfortable doing,
> or should I be looking to volunteer someone else to get this task done?
>
> Andrew
>
>
> Mark Boyd wrote:
>
> Just push it in as is. There is no history to maintain other than the fact
> that it was contributed prior to my leaving sungard in prep for the
> developer's conference. But that is understood already and should not be an
> issue.
>
> Mark
>
> On 7/25/07, Andrew Petro <[EMAIL PROTECTED]> wrote:
> >
> > No, there is not a Fisheye view of the CVS sandbox.  Fisheye pointing at
> > CVS was disabled due to performance problems.
> >
> > JA-SIG Fisheye now only points at 
> > SVN<http://developer.ja-sig.org/source/browse/jasigsvn>
> > .
> >
> > JA-SIG CVS is read-only and deprecated at this time.  The CVS sandbox
> > code should be moved into a (new?) SVN module.
> >
> > Mark, is the revision history of the "DLM 2.0" sandbox code valuable, or
> > would it be best to simply commit the current state of that code de novo
> > into a new SVN location to establish a new JA-SIG source control sandbox?
> >
> > Andrew
> >
> >
> > Mark Boyd wrote:
> >
> > Does anyone know if there is a fisheye view of the sandbox?
> >
> > Mark
> >
> >
> --
> You are currently subscribed to [email protected] as: [EMAIL 
> PROTECTED]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>

-- 
You are currently subscribed to [email protected] as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to