Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
ee40e8f5
Commit
ee40e8f5
authored
Oct 02, 2001
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi Fix typo in support section.
Docs/manual.texi: Fix typo in support section.
parent
9b82dee6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
8 deletions
+1
-8
Docs/manual.texi
Docs/manual.texi
+1
-8
No files found.
Docs/manual.texi
View file @
ee40e8f5
...
...
@@ -2723,16 +2723,9 @@ Almost any problem involving MySQL is important to us if it's
important to you. Typically customers seek help on how to get
different commands and utilities to work, remove performance
bottlenecks, restore crashed systems, understand operating system
or networking impacts on MySQL, establish best practi
s
es for backup
or networking impacts on MySQL, establish best practi
c
es for backup
and recovery, utilize APIs, etc.
We consider reliability to be crucial to MySQL's success, and
fixing bugs is important to us. If you discover a bug that can
be repeated reliably, we will fix it in any case. But if you pay
for support we will also notify you about the fix status instead
of just fixing it in a later release.
@xref{Bug reports}.
@node Copyright, Licensing policy, Support, Licensing and Support
@subsection Copyrights Used by MySQL
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment