> ones with commit access set the priorities. (Still, it would be nice at
> least to have typos fixed in README.SMP ;)
Doesn't take much to do that; if you see the typos why not submit a diff?
-f
http://www.blackant.net/ - README.SMP.o Thu Mar 20 21:45:48 2003
+++ README.SMP Thu Mar 20 21:50:11 2003
@@ -1,10 +1,10 @@
-The SMP branch is irregularily updated from the trunk. To do this
+The SMP branch is irregularly updated from the trunk. To do this
you mainly need to carry out the following procedure.
- Determine the new synchronization tag to use. There are two used
alternately; SMP_SYNC_A and SMP_SYNC_B. You can use several hueristics
to find out which one was used last, and then use the other one.
- For example, CVSROOT/history* files gives you information about tag
+ For example, CVSROOT/history* files give you information about tag
operations in lines matching '^T'. Call the tag you will be using
for $NEW_TAG and the other one $OLD_TAG.
@@ -18,7 +18,7 @@
$ cvs get -rSMP -kk src/sys
- Go into src/sys and merge from the trunk (make sure that the repository
- you use have the new tags from the tagging above, i.e. don't use a
mirror
+ you use has the new tags from the tagging above, i.e. don't use a
mirror
that has not been updated since that step):
$ cvs up -j$OLD_TAG -j$NEW_TAG -kk
@@ -36,7 +36,7 @@
I) Readdition of files that have gone dead. They need to have
the timestamp in the Entries file changed to /dummy timestamp/
in order to be accepted by commit.
- II) Under som circumstances cvs just bombs on a file leaving it
+ II) Under some circumstances cvs just bombs on a file leaving it
updated and locked in the repository. In that case something
like this is needed:
@@ -53,4 +53,4 @@
$ cvs -q rdiff -u -r$NEW_TAG -rSMP
- It should just by differences related to multiprocessor support.
+ It should just be differences related to multiprocessor support.
Received on Thu Mar 20 21:59:03 2003
This archive was generated by hypermail 2.1.8
: Wed Aug 23 2006 - 13:46:07 EDT
|