- #SVN ADD NEW FILES HOW TO#
- #SVN ADD NEW FILES CODE#
- #SVN ADD NEW FILES PASSWORD#
- #SVN ADD NEW FILES ZIP#
Svn propdel svn:executable src/read_CAMAC.c To remove the executable permission from a file in the repository, do this: Svn mkdir r282.iTOP-module-used-at-LEPS-SPRING8/Ĭd r282.iTOP-module-used-at-LEPS-SPRING8/ To make a reference to a useful previous state of the repository (called a "tag"), use the svn copy function: It can also be from a different location in the current revision of the repo. Svn copy -r 344 boardstack-v2-with-SCROD-revA2.ucf. To resurrect a "dead" file from an earlier version of the repository, do the following: To add specific files/directories, they must be listed one file or filespec per line (on the command-line, do this with ctrl-enter): Which ignore all files not specifically added to the repository in that directory (it acts recursively). I uploaded useful bit files that have been generated for this project into the "downloads" section of the website: so that they don't clutter up the repository.įor the files that don't belong in the repository that show up with an annoying "? filename" anytime you do a svn commit or svn status command, you can tell it to ignore them in the future with the following command: Note that this is just the regular "trunk" checkout command, but with a slightly shorter URL because it's a parent of a parent directory.
Svn checkout idlab-scrod -username "username" with your own google username. To get the whole repository (including the wiki, the trunk, all branches and tags), give this command:
#SVN ADD NEW FILES CODE#
After those versions compile and nominally work or the test / side-project is completed, the code from those branches can be "merged" with the main "trunk" line of development if desired. Examples would be the "USB tester" version that User#1 made, the "blinkenlights" version that User#2 made or the "16x ASICs" version that User#3 made.
To be distinguished from the "trunk" version are "branches." These are for allowing experimental or partially working code to be committed without disturbing the other users of the repository. You can see the latest version of the code that's in the repository here on the web with a cutsie interface: There are links at the top to get elsewhere in the repository (like other subprojects or the wiki files).
#SVN ADD NEW FILES ZIP#
Which will make a dir in the current dir called "idlab-scrod" or whatever you put at the end there and then you can do what you like with it (with the benefit being you don't have to post/transfer 70MB zip files anymore). If you just want a copy of the files to zip up and put on the blog or email to someone, this is the way to do it:
#SVN ADD NEW FILES HOW TO#
More instructions are at (including how to get your google code password, which only seems necessary once and only when you first try to commit something to the repository). Svn checkout idlab-scrod -username the given username with your own. If you want to checkout the latest and greatest copy of the code (the so-called "trunk" version), this is the command to use: Note that you must perform the "svn add" command on that file before it will allow you to commit it.
#SVN ADD NEW FILES PASSWORD#
It might ask you for your password at this point if you haven't entered it before. With whatever comment text you like (-m is for comment), even if it's an empty string. Svn commit -m "initial add of some vhdl that counts pulses coming out of the zargblaster ASIC" Once you're happy with the content of a file you want to put in the repository (whether you've committed that file before or not), commit the change with the following: Lines that indicate you haven't told it what to do with those other files yet (which is fine).Ĭommitting files (the most common command) Then make sure it hasn't added anything crazy (like a bunch of unwanted output files) with: To add a file to the repository, type the following: