diff options
| author | Nathan Kidd <nkidd@opentext.com> | 2014-01-03 16:44:00 -0700 |
|---|---|---|
| committer | Brian Paul <brianp@vmware.com> | 2014-01-06 09:55:38 -0700 |
| commit | 0691b37732e3b032fbd354537b20090a3ee8e122 (patch) | |
| tree | 4883628a61a373fb6c9af69231b5433fa97d01f3 /docs/devinfo.html | |
| parent | a61ae2aa01c9b1976ba4107c1564e0c3f94aea4d (diff) | |
docs: fix misspellings
Fixed what I noticed; no warranty for exhaustiveness.
Signed-off-by: Nathan Kidd <nkidd@opentext.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Diffstat (limited to 'docs/devinfo.html')
| -rw-r--r-- | docs/devinfo.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/devinfo.html b/docs/devinfo.html index a9d8b4f7db8..d4a6dfb590d 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -206,7 +206,7 @@ exclusively for the older branch. This "CC" syntax for patch nomination will cause patches to automatically be copied to the mesa-stable@ mailing list when you use "git send-email" to send patches to the mesa-dev@ mailing list. Also, if you realize that a commit -should be nominate for the stable branch after it has already been commited, +should be nominated for the stable branch after it has already been committed, you can send a note directly to the mesa-stable@lists.freedesktop.org where the Mesa stable-branch maintainers will receive it. Be sure to mention the commit ID of the commit of interest (as it appears in the mesa master branch). |