Thread: [Pyallegro] Switching to SVN?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hey. How about switching the repositories to SVN? This doesn't
imply CVS is going to be dropped, since SF offers having both.
If you are happy with CVS you could keep using it.

Just noticed this message, and I'm really thumbs up for SVN.

~ AKX.

On 3/12/06, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> Hey. How about switching the repositories to SVN? This doesn't
> imply CVS is going to be dropped, since SF offers having both.
> If you are happy with CVS you could keep using it.

On 2006-03-13, AKX <th...@gm...> wrote:
> Just noticed this message, and I'm really thumbs up for SVN.

I'll request the SVN repository soon (SF is down due to maintenance).

On 2006-03-13, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> I'll request the SVN repository soon (SF is down due to maintenance).

Done. Automatic migration of the current CVS
repository is pending. SF docs about SVN are at:
http://sourceforge.net/docs/E09. Apparently the most interesting
stuff is:

    Subversion Server:  https://svn.sourceforge.net
    Path to Repository: /svnroot/pyallegro

I wonder about the /svnroot/ part, since you already access
svn.sourceforge.net...

>     Subversion Server:  https://svn.sourceforge.net
>     Path to Repository: /svnroot/pyallegro
> 
> I wonder about the /svnroot/ part, since you already access
> svn.sourceforge.net...

So they are using https and wonder about poor SVN
performance... anyway, the import is done I believe the first
thing should be to reorganise the hiearchy. Since both projects
are different, instead of the typical branch-trunk-tag/project we
could move it to project/branch-trunk-tag.

Is that ok?

Well, I don't really care.
Do what you think is best.. I just want to do commits and updates ;)

On 3/15/06, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> >     Subversion Server:  https://svn.sourceforge.net
> >     Path to Repository: /svnroot/pyallegro
> >
> > I wonder about the /svnroot/ part, since you already access
> > svn.sourceforge.net...
>
> So they are using https and wonder about poor SVN
> performance... anyway, the import is done I believe the first
> thing should be to reorganise the hiearchy. Since both projects
> are different, instead of the typical branch-trunk-tag/project we
> could move it to project/branch-trunk-tag.
>
> Is that ok?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

On 2006-03-15, AKX <th...@gm...> wrote:
> Well, I don't really care.
> Do what you think is best.. I just want to do commits and updates ;)

Done. Root is http://svn.sourceforge.net/viewcvs.cgi/pyallegro/,
with alpy and pyrex subdirectories. In order to work with pyrex
you would do:

 svn co https://svn.sourceforge.net/svnroot/pyallegro/pyrex/trunk pyrex

I could do all the structure reshuffling in a single commit without
net access. Really cool. I just wish there was some kind of log
cache, because I use that feature quite often.

Right. I'll abandon updating the CVS now, if that's OK - mostly
because I like SVN a lot more... so if you want to do some
deleting/archiving (attic? dunno) or other stuff for the CVS, perhaps
some notice that further development will be in SVN, or something, go
ahead :)

I'll try to wrap a couple new functions in the near(ish) future, for
example background_mode is a good thing to have.

AKX.

On 3/15/06, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2006-03-15, AKX <th...@gm...> wrote:
> > Well, I don't really care.
> > Do what you think is best.. I just want to do commits and updates ;)
>
> Done. Root is http://svn.sourceforge.net/viewcvs.cgi/pyallegro/,
> with alpy and pyrex subdirectories. In order to work with pyrex
> you would do:
>
>  svn co https://svn.sourceforge.net/svnroot/pyallegro/pyrex/trunk pyrex
>
> I could do all the structure reshuffling in a single commit without
> net access. Really cool. I just wish there was some kind of log
> cache, because I use that feature quite often.
>

On 2006-03-16, AKX <th...@gm...> wrote:
> Right. I'll abandon updating the CVS now, if that's OK - mostly
> because I like SVN a lot more...

Sure, that's the idea.

> so if you want to do some deleting/archiving (attic? dunno)
> or other stuff for the CVS, perhaps some notice that further
> development will be in SVN, or something, go ahead :)

It doesn't hurt keeping it there, at least for a few months.