List:Internals« Previous MessageNext Message »
From:stefan Date:December 10 2003 12:46pm
Subject:bk commit - mysqldoc tree (Administrator:1.1055)
View as plain text  
Below is the list of changes that have just been committed into a local
mysqldoc repository of Administrator. When Administrator does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.1055 03/12/10 13:46:25 Administrator@athena. +1 -0
  manual.texi:
    256M isn't "much memory" nowadays

  Docs/manual.texi
    1.986 03/12/10 13:45:38 Administrator@athena. +2 -2
    256M isn't "much memory" nowadays

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	Administrator
# Host:	athena.
# Root:	C:/cygwin/home/Administrator/mysqldoc

--- 1.985/Docs/manual.texi	Wed Dec 10 06:15:14 2003
+++ 1.986/Docs/manual.texi	Wed Dec 10 13:45:38 2003
@@ -32991,13 +32991,13 @@
 For variable names that end in @code{_size}, you may need to specify them
 without @code{_size}. For example, the old name for @code{sort_buffer_size} is
 @code{sort_buffer}. The old name for @code{read_buffer_size} is
-@code{record-buffer}. To see which variables your version of the server
+@code{record_buffer}. To see which variables your version of the server
 recognizes, use @code{mysqld --help}.
 
 @end itemize
 
 
-If you have much memory (at least 256M) and many tables and want maximum
+If you have at least 256M of memory and many tables and want maximum
 performance with a moderate number of clients, you should use something
 like this:
 
Thread
bk commit - mysqldoc tree (Administrator:1.1055)stefan10 Dec