From: Mark M. <mie...@gm...> - 2011-03-23 16:06:56
|
All, The basic structure of the subversion repository for the project has been set up. This is just some basic notes about subversion (which a lot of times I just call svn) and the current structure of the RexxTill repository. The URL for the repository is: https://rexxtill.svn.sourceforge.net/svnroot/rexxtill You can check out the entire repository using that URL and a subversion client. The repository is basically just a set of empty directories at this point. Subversion is essentially a directory / file orientated versioning system. This is the current directory structure. RexxTill\branches\ RexxTill\releases\ RexxTill\trunk\ docs\branches\ docs\releases\ docs\trunk\design sandbox\ svnconfig\config An easy way to visualize the layout of a subeversion repository on SourceForge is to use the svn browse tool. This page is a direct link to the one for the RexxTill project: http://rexxtill.svn.sourceforge.net/viewvc/rexxtill/ RexxTill\trunk is where the source code for RexxTill would go, with subdirectories created as needed. Documentation related stuff would go in docs\trunk. A subdirectory is already created there for design docs: docs\trunk\design. Jon has already added a file there. sandbox is an area where committers can commit stuff that is not ready to go into the, for lack of a better word, 'real' source code base. In most projects there is usually no restrictions on what committers can use the sandbox for. Although normally it is an unspoken rule that the area is for stuff related to the project. svnconfig\ just contains a single file: 'config' That file is a base subversion configuration file modified to be of use for RexxTill. It is the suggested file for committers on the project and, when used, will automatically set the properties of files committed to the project, based on their file extension. It is a slightly modified version of the ooRexx project file. That is most of the really pertainent data on the repsository. If anyone still has any question, just ask. I have posted on RexxLA, the ooRexx lists, and on comp.lang.rexx dozens of times on how to check out code using a svn client, so I'm not going to post here how to do it. But, if anyone has questions on how to do that, just ask and I will post with a different subject heading on what to do. -- Mark Miesfeld |
From: Rony G. F. <Ron...@wu...> - 2011-03-23 16:48:31
|
Mark, *great work*, kudos to you !! Just a hint for those, who are command-line aficionados and have "svn" available via the commandline: you can download the svn files with the following command: svn co https://oorexx.svn.sourceforge.net/svnroot/rexxtill rexxtill Then, anytime something changed in that svn repository you can get the changes by issuisng from the "rexxtill"-directory: svn update If you change/add something (if you have commit rights), then you could use the following command to upload your changes/addition to the Sourceforge svn-repository: svn ci -m "a message describing the changes/additions" HTH, ---rony P.S.: Wished I was as able and quick to setup the mailing lists and svn repository for the BSF4ooRexx project! On 23.03.2011 17:06, Mark Miesfeld wrote: > All, > > The basic structure of the subversion repository for the project has > been set up. > > This is just some basic notes about subversion (which a lot of times I > just call svn) and the current structure of the RexxTill repository. > > The URL for the repository is: > > https://rexxtill.svn.sourceforge.net/svnroot/rexxtill > > You can check out the entire repository using that URL and a > subversion client. The repository is basically just a set of empty > directories at this point. > > Subversion is essentially a directory / file orientated versioning system. > > This is the current directory structure. > > RexxTill\branches\ > RexxTill\releases\ > RexxTill\trunk\ > docs\branches\ > docs\releases\ > docs\trunk\design > sandbox\ > svnconfig\config > > An easy way to visualize the layout of a subeversion repository on > SourceForge is to use the svn browse tool. This page is a direct link > to the one for the RexxTill project: > > http://rexxtill.svn.sourceforge.net/viewvc/rexxtill/ > > RexxTill\trunk is where the source code for RexxTill would go, with > subdirectories created as needed. > > Documentation related stuff would go in docs\trunk. A subdirectory is > already created there for design docs: docs\trunk\design. Jon has > already added a file there. > > sandbox is an area where committers can commit stuff that is not ready > to go into the, for lack of a better word, 'real' source code base. > In most projects there is usually no restrictions on what committers > can use the sandbox for. Although normally it is an unspoken rule > that the area is for stuff related to the project. > > svnconfig\ just contains a single file: 'config' That file is a base > subversion configuration file modified to be of use for RexxTill. It > is the suggested file for committers on the project and, when used, > will automatically set the properties of files committed to the > project, based on their file extension. It is a slightly modified > version of the ooRexx project file. > > That is most of the really pertainent data on the repsository. If > anyone still has any question, just ask. > > I have posted on RexxLA, the ooRexx lists, and on comp.lang.rexx > dozens of times on how to check out code using a svn client, so I'm > not going to post here how to do it. But, if anyone has questions on > how to do that, just ask and I will post with a different subject > heading on what to do. > > -- > Mark Miesfeld > |
From: Sahananda (J. W. <sah...@wi...> - 2011-03-23 17:57:41
|
On 23 March 2011 16:48, Rony G. Flatscher <Ron...@wu...> wrote: > Mark, > > *great work*, kudos to you !! > Yes, I want to add my apreciation to Rony's - you have been great Mark. Jon |