Laurent ROCHER wrote: > I have play a little with CVS, and i think i can setup CVS like this.
good news. I can play with CVS, but I know almost nothing about branches. > 1) Tag current CVS source code as Win32-GUI-0_0_622. > I have notice a problem with text files. Each line end with CRCRLF. > I found this in TortoiseCVS FAQ : > http://www.tortoisecvs.org/faq.html#sharelinux > I have fix this in my home repository, so i can correct it before. > 2) Upload 665 code and tag it as Win32-GUI-0_0_665 > 3) Make a Win32-GUI-0_0_665-Fix branch and use this branch for fix bug. > So, we can continue to use main branch for new version. sounds perfectly reasonable. > If you are agree, i can do the job and start to work on 665 fix branch. > I probably take a look on next release too ;) ok. you should already have write access to the CVS, so you can start as soon as you want. let me know when you are done (and let me know the commands to access a specific branch, because I never did it :-). > Kwiki it's a good idea. It's very easy to install/customize/use. > Why not use SourceForge Web Space (i read somewhere it's possible to use > perl cgi). yes, I'll look into it. cheers, Aldo __END__ $_=q,just perl,,s, , another ,,s,$, hacker,,print;
