Once you have a Bochs directory, you can compile the files, edit them, test them, etc.
See the documentation section, Tracking the source code with SVN
for more info on SVN, in the User Manual. But what's new and different is that
you can now do SVN commits. When a file is all fixed and ready to share with the rest of
the world, you run a commit command to upload your version to the server.
First, it's good to do a SVN update to make sure nobody else has changed it
since you downloaded it last. At the first commit you'll always have to specify your
SF username and type your password.
$ svn update file.cc
$ svn commit --username sfusername file.cc
[editor opens. type log message, save, and exit.]
Login area: <https://bochs.svn.sourceforge.net:443> SourceForge Subversion area
Username: sfusername
Password for 'sfusername': <--type your password
Sending file.cc
Transmitting file data .
Committed revision 10. |
When SVN starts an editor, The default is usually vi. If you want a different
editor, set the EDITOR environment variable to the name of your preferred
editor. When you're done, just save the file and quit the editor. Unless
there's some problem, you will see a message that says what the new revision
number for the file is, and then "done". If while you're editing the log
message, you decide that you don't want to commit after all, don't save the
file. Quit the editor, and when it asks where the log message went, tell it
to abort.
Here is an example of a successful checkin:
$ svn commit misc.txt
[edit log msg]
Sending misc.txt
Transmitting file data .
Committed revision 6. |
And here is an aborted one:
$ svn commit misc.txt
[quit editor without saving]
Log message unchanged or not specified
a)bort, c)ontinue, e)dit:
a |