mirrors/Bochs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

some more docs updates with cvs->svn transition

Browse Source
This commit is contained in:
Stanislav Shwartsman 2011-11-07 19:20:11 +00:00
parent 39ddc75098
commit 801a3f920f
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bochs/Makefile.in
View File

@ -583,7 +583,7 @@ SETFILE=/Developer/Tools/SetFile
# the SF compile farm through an ssh connection because osacompile
# needs to be run locally for some reason. Solution: If the script
# sources are changed, rebuild the executable on a MacOSX machine,
# split it into its data and resource forks and check them into CVS
# split it into its data and resource forks and check them into SVN
# as separate files. Then at release time, all that's left to do is
# put the data and resource forks back together to make a working script.
# (This can be done through ssh.)
@ -608,7 +608,7 @@ test_hfsplus:
# Step 1 (must be done locally on MacOSX, only when sources change)
# Compile and pull out just the resource fork. The resource fork is
# checked into CVS as script_compiled.rsrc. Note that we don't need
# checked into SVN as script_compiled.rsrc. Note that we don't need
# to check in the data fork of tmpscript because it is identical to the
# script.data input file.
$(SCRIPT_COMPILED_RSRC): $(SCRIPT_R) $(SCRIPT_APPLESCRIPT)

8
bochs/README
View File

@ -29,10 +29,10 @@ GETTING CURRENT SOURCE CODE
Source code for Bochs is available from the Bochs home page at
http://bochs.sourceforge.net. You can download the most recent
release, use CVS to get the latest sources, or grab a CVS
release, use SVN to get the latest sources, or grab a SVN
snapshot which is updated nightly. The releases contain the most
stable code, but if you want the very newest features try the
CVS version instead.
SVN version instead.
WHERE ARE THE DOCS?
@ -68,11 +68,11 @@ of recent messages to see what's going on.
If you are a technical person (can follow hardware specs, can write
C/C++) take a look at the list of open bug reports and feature
requests to see if you are interested in working on any of the
problems that are mentioned in them. If you check out the CVS
problems that are mentioned in them. If you check out the SVN
sources, make some changes, and create a patch, one of the
developers will be very happy to apply it for you. Developers who
frequently submit patches, or who embark on major changes in the
source can get write access to CVS. Be sure to communicate with the
source can get write access to SVN. Be sure to communicate with the
bochs-developers list to avoid several people working on the same
thing without realizing it.

6
bochs/TODO
View File

@ -76,7 +76,7 @@ documented cards, or one could even use a real spare vga card.
Frank Cornellis has done a great job on this subject, and we began
integrating his changes.
Status:
The pcidev device is present in CVS and it has been updated for the new PCI
The pcidev device is present in SVN and it has been updated for the new PCI
infrastructure, but the new code is untested yet.
5. Subdirectories in iodev
@ -118,7 +118,7 @@ In the Etherboot project's CVS, in the contrib/bochs directory, you can
find a working bochsrc file and an up-to-date README with step-by-step
instructions on getting this working.
Status:
The pnic device is present in CVS, but the status is unknown.
The pnic device is present in SVN, but the status is unknown.
9. Bios
9.1 add "jump table placeholder" and log missing function calls in the bios.
@ -209,7 +209,7 @@ There is some progress, but still a lot of work to do.
If you want to help without coding, here are available positions :
19.1 Webmaster : update website (Jan Bruun Andersen offered to help)
19.2 patch coordonator : look at incoming patches (sourceforge and
mailing list) and upload / update in the cvs patches directory.
mailing list) and upload / update in the SVN patches directory.
19.3 platform maintainers for macos / win32
19.4 disk image maintainer : create and maintain our collection
of disk images. Usually, only the configuration file needs to be

4
bochs/patches/HEADER
View File

@ -7,9 +7,9 @@ Status:
Detailed description:
Patch was created with:
cvs diff -u
diff -up VER1 VER2
Apply patch to what version:
cvs checked out on DATE, release version VER
svn revision [REVISION]
Instructions:
To patch, go to main bochs directory.
Type "patch -p0 < THIS_PATCH_FILE".