diff options
| author | Tor Lillqvist <tml@iki.fi> | 2013-05-15 10:42:04 +0300 |
|---|---|---|
| committer | Tor Lillqvist <tml@iki.fi> | 2013-05-15 11:14:28 +0300 |
| commit | cb6d67c21f11811c5bc023b9565c1c1b1f4081fa (patch) | |
| tree | ff8a4b192a2ca846d32111732563432244135910 /libmariadb | |
| parent | 1a357b7394ac7b48b72821bff1aae4706265d7a4 (diff) | |
Spelling "separate" (etc) correctly is hard
Diffstat (limited to 'libmariadb')
| -rw-r--r-- | libmariadb/mariadb-trunk-40.patch | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/libmariadb/mariadb-trunk-40.patch b/libmariadb/mariadb-trunk-40.patch index de8f44ca2c10..968a75048ebd 100644 --- a/libmariadb/mariadb-trunk-40.patch +++ b/libmariadb/mariadb-trunk-40.patch @@ -41460,7 +41460,7 @@ + int sz; /* Bytes of memory required to allocate the new cache */ + + /* -+ ** The seperateCache variable is true if each PCache has its own private ++ ** The separateCache variable is true if each PCache has its own private + ** PGroup. In other words, separateCache is true for mode (1) where no + ** mutexing is required. + ** @@ -47573,7 +47573,7 @@ +** page is initialized to all zeros. +** +** If noContent is true, it means that we do not care about the contents -+** of the page. This occurs in two seperate scenarios: ++** of the page. This occurs in two separate scenarios: +** +** a) When reading a free-list leaf page from the database, and +** @@ -66368,7 +66368,7 @@ +** the blob of data that it corresponds to. In a table record, all serial +** types are stored at the start of the record, and the blobs of data at +** the end. Hence these functions allow the caller to handle the -+** serial-type and data blob seperately. ++** serial-type and data blob separately. +** +** The following table describes the various storage classes for data: +** @@ -88072,7 +88072,7 @@ + /* Drop all SQLITE_MASTER table and index entries that refer to the + ** table. The program name loops through the master table and deletes + ** every row that refers to a table of the same name as the one being -+ ** dropped. Triggers are handled seperately because a trigger can be ++ ** dropped. Triggers are handled separately because a trigger can be + ** created in the temp database that refers to a table in another + ** database. + */ |