Hmmmmmm. This is proving to be a real pain in the rear end. Alright. I can start over and try and do the conversion, but it will take me a few more days.
I think at some point we need to do a freeze on the commits to the CVS so I am sure that everything is captured in the conversion process. We don't need to do this yet because it will probably take me a day or two to get the tools set up and figure out what the heck I am doing. SS On 6/13/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote: > Hei all and Landon > > i know I didn't do anything for the svn setup right now, so i am in a > weak position for advises. But may i suggest that we try a *new setup* > of the svn repository by using the Sourceforge tools and following their > guidelines (which i haven't read)? > > Because it would be beneficial if we could save by that the history of > the last 400 cvs commits. > Note, that there have been 5 commits in the last 24 hours by michael and > Stephan. > > sorry if that creates more work - but we should have the time for that. > If it is not possible to save the history we can leave the things as > they are. > > stefan > > Sunburned Surveyor schrieb: > > I probably missed them. I will add them. > > > > SS > > > > On 6/13/07, Sascha L. Teichmann <[EMAIL PROTECTED]> wrote: > >> Hi! > >> > >> What about the ChangeLog, Changes.txt and TODO.txt? > >> I cannot find them in the SVN trunk. > >> > >> Regards, Sascha > >> > >> Sunburned Surveyor schrieb: > >>> I'm afraid I was already well into the process of setting up the SVN > >>> when I read the helpful e-mails in this thread. :[ > >>> > >>> I have made a stab at setting up the SVN for OpenJUMP at the JPP, and > >>> it *may* be ready for use. > >>> > >>> I made a "trunk" and "branches" folders under the "openjump" folder. I > >>> then created a branch of "trunk" in the "branches/stable" folder. This > >>> included the scripts, installers, etc., not just the "trunk/src" > >>> folder. This will allow us to version all elements of the release, not > >>> just the source code. I can change this if it is not acceptable. > >>> > >>> I also see everyone has SVN access. > >>> > >>> Can someone check my work on the SVN before we decide to "go live" > >>> with it. It is totally possible that I have royally messed things up. > >>> > >>> The Sunburned Surveyor > >>> > >>> P.S. - When we do "go live" changes to OpenJUMP should go in the trunk. > >>> After they have been "approved" (however that works) we can move them > >>> to the stable branch. > >>> > >>> P.S.S. - Might I suggest that we adopt a "suggested" format for commit > >>> comments? I lined out some really basic guidelines for the SurveyOS > >>> Project Subversion Repository. I'm not saying we should require > >>> developers follow something similar, just that we "suggest" they do. > >>> > >>> http://surveyoswiki.pbwiki.com/SurveyOS+Subversion+Repository+Usage+Guidelines > >>> > >>> (I know that having a simple commit log format could help if we wantd > >>> to use some scripts or parsing tools of the SVN logs in the future. At > >>> least that is what I read in one of my SVN books.) > >>> > >>> ------------------------------------------------------------------------- > >>> This SF.net email is sponsored by DB2 Express > >>> Download DB2 Express C - the FREE version of DB2 express and take > >>> control of your XML. No limits. Just data. Click to get it now. > >>> http://sourceforge.net/powerbar/db2/ > >>> _______________________________________________ > >>> Jump-pilot-devel mailing list > >>> Jump-pilot-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by DB2 Express > >> Download DB2 Express C - the FREE version of DB2 express and take > >> control of your XML. No limits. Just data. Click to get it now. > >> http://sourceforge.net/powerbar/db2/ > >> _______________________________________________ > >> Jump-pilot-devel mailing list > >> Jump-pilot-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
