summaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* swr: clean up supported OGL4.0/4.1 extensions listJan Zielinski2019-05-161-4/+4
| | | | | | | | | | | | This commit adjusts the capabilities returned by the SWR driver and the documentation to correctly report the following extensions: GL_ARB_texture_query_lod, GL_ARB_texture_cube_map_array, GL_ARB_gpu_shader_fp64, GL_ARB_texture_gather, GL_ARB_vertex_attrib_64bit. Reviewed-by: Alok Hota <[email protected]>
* docs: advice to resolve discussion on gitlab MR docAlejandro Piñeiro2019-05-161-0/+3
| | | | | | | | | | | | | | For newcomers to gitlab, it is not evident that it is better to press the "Resolve Discussion" button when you update your branch handling feedback. v2: * Fix several grammar nits, reorder, use new corrected text (Connor Abbot) * Use "reviewers", instead of reviewer (Eric Engestrom) Reviewed-by: Connor Abbott <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: update calendar, and news item and link release notes for 19.0.4Dylan Baker2019-05-093-7/+8
|
* docs: Add SHA256 sums for mesa 19.0.4Dylan Baker2019-05-091-1/+2
|
* Docs: add 19.0.4 release notesDylan Baker2019-05-091-0/+242
|
* docs: drop h1 in headerErik Faye-Lund2019-05-08274-279/+274
| | | | | | | | | | | It's generally frowned upon to have more than one H1 per document in HTML4. So let's put the text directly inside the header. This means we can drop the flex-based centering, which makes things a bit easier. We also need to change the padding to rem instead of em, because the em has now changed. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: harmonize headings and titlesErik Faye-Lund2019-05-0812-23/+23
| | | | | | | | | | | | | We're pretty insonsistent in what the headings and titles are, especially compared to what the articles are listed as in the sidebar. Let's harmonize this. There's a notable exception for meson.html, where the sidebar uses a short-hand form that makes sense in the sidebar, but not in the article due to the visible context being different. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: renumber headingsErik Faye-Lund2019-05-0810-83/+87
| | | | | | | | | | | | It's generally frowned upon to have multiple H1 headings in HTML4. So let's make sure each article has a primary heading for the article, and that that heading is the title that is used in the sidebar. While we're at it, let's update the title in the articles to match the title from the sidebar as well. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: give download-article a primary headingErik Faye-Lund2019-05-081-5/+7
| | | | | | | | | | | | It's generally frowned upon to have multiple H1 headings in HTML4. So let's add a primary heading for the article, and source that from the title used in the sidebar. While we're at it, let's update the title in the article to match the title from the sidebar as well. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: use title-casing for all headings in sidebarErik Faye-Lund2019-05-081-10/+10
| | | | | | | | | We generally use title-casing for headings in the sidebar. But not all headings was constently cased like that. Let's make sure this is consistent. Signed-off-by: Erik Faye-Lund <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* docs: spell out "and" in sidebarErik Faye-Lund2019-05-081-3/+3
| | | | | | | | | There's no need to keep this short, we can just spell out "and" here. Besides, a slash kind of implies "or", but these articles are about both of these, not either. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: remove pointless list-entryErik Faye-Lund2019-05-081-1/+0
| | | | | | | | It's quite visible that there's more docs below, we don't need to spell it out for the reader. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: spell out faq in sidebarErik Faye-Lund2019-05-081-1/+1
| | | | | | | | We're not short on space here, so there's little point in abbreviating this. This also matches the heading in the article. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: spell out "and" in sidebarErik Faye-Lund2019-05-081-1/+1
| | | | | | | | | We're not short on space here, so let's just spell out "and" instead of using the ampersand. This is more consistent with the entry above in the sidebar. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: Add relnotes stub for 19.2Juan A. Suarez Romero2019-05-071-0/+59
| | | | Signed-off-by: Juan A. Suarez Romero <[email protected]>
* doc: Update GL_KHR_robustness in features.txt for r600Uros Bizjak2019-05-071-8/+8
| | | | | | | | glxinfo for Cypress XT [Radeon HD 5870] lists GL_KHR_robustness as supported extension. This was the last missing extension for GL 4.5, so Mark GL 4.5 as all DONE for r600. Reviewed-by: Dave Airlie <[email protected]>
* docs: fixup mistake in contentsErik Faye-Lund2019-05-021-4/+0
| | | | | | | | | | | | During a rebase, it seems I accidentally broke the contents-menu, leading to a duplicate link to freedesktop.org. This was obviously not intended. Let's fix this. Signed-off-by: Erik Faye-Lund <[email protected]> Fixes: 7eee13c4679 ("docs: use dl/dd instead of blockquote for freedesktop link") Reviewed-by: Dylan Baker <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: mark KHR_blend_equation_advanced done on a6xxRob Clark2019-05-021-1/+1
| | | | Signed-off-by: Rob Clark <[email protected]>
* svga: add SVGA_NO_LOGGING env var (v2)Brian Paul2019-05-021-0/+3
| | | | | | | | | | valgrind crashes when we try to initialize host logging. This env var can be used to disable logging. v2: rebase onto "svga: move host logging to winsys". Cc: [email protected] Reviewed-by: Neha Bhende <[email protected]>
* docs: reorder heading and noticeErik Faye-Lund2019-05-021-4/+2
| | | | | | | | All other pages has the heading as ghe first thing in the article. Let's clean this up for consistency. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: drop centered heading for faqErik Faye-Lund2019-05-021-2/+0
| | | | | | | | | The FAQ is the only article we have that uses a centered heading, which makes it look odd compared to the other articles. Let's drop the centering for consistency. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: turn faq-index into an ordered listErik Faye-Lund2019-05-021-8/+6
| | | | | | | | HTML already have a way of doing automatically ordered lists, so let's use that instead of open-coding one. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: replace empty list with a none-paragraphErik Faye-Lund2019-05-021-4/+1
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: fix closing of list-itemsErik Faye-Lund2019-05-022-2/+2
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: fixup list-item tagsErik Faye-Lund2019-05-021-4/+4
| | | | | | | | The list items needs to contain everything part of the item, not just the first paragraph. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: fix closing of paragraphsErik Faye-Lund2019-05-022-2/+2
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: add missing listsErik Faye-Lund2019-05-022-0/+4
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: fixup bad paragraphingErik Faye-Lund2019-05-021-5/+5
| | | | | | | | This markup seems to assume paragraphs survive across block-elements, which isn't the case. Let's rectify that. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: remove stray list-startErik Faye-Lund2019-05-021-4/+0
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: don't pointlessly close and re-start definition listsErik Faye-Lund2019-05-021-4/+0
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: fix incorrectly closed paragraphErik Faye-Lund2019-05-021-1/+2
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: drop paragraph around preformatted textErik Faye-Lund2019-05-021-2/+0
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: start paragraph before closing itErik Faye-Lund2019-05-021-0/+1
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: close paragraphs before preformatted textErik Faye-Lund2019-05-024-6/+8
| | | | | | | | | | | It's illegal to nest block-level elements such as <pre> inside <p> in HTML. This means that when the paragraphs gets closed after a <pre>-tag, we end up closing a non-existent tag, so the browser inserts a dummy <p>-tag. This is entirely pointless, so let's just close these tags before the <pre>-tag instead. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: remove stray paragraph-closeErik Faye-Lund2019-05-021-1/+0
| | | | | | | This isn't matching any paragraph-open tags, so let's get rid of it. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: close listsErik Faye-Lund2019-05-023-1/+5
| | | | | | | | These lists never got closed. Let's fix that to avoid issues with bad parsers. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: close paragraphs before listsErik Faye-Lund2019-05-026-23/+23
| | | | | | | | | paragraphs can't contain lists, and attempting to close them after the list just cause an extra, empty paragraph to be created. We don't want that, so let's close the paragraphs before the list intead. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: open list-item before closing itErik Faye-Lund2019-05-021-1/+1
| | | | | | | | A list-item must be openened before it can be closed. So let's replace this closing tag with an opening tag. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: use dl/dd instead of blockquote for freedesktop linkErik Faye-Lund2019-05-021-0/+3
| | | | | | | | | | | | | The blockquote happens to match the indentation of the other lists for most browsers, but this isn't a guarantee. Let's instead use a definition-list, which is more strongly connected to a list, so it's more likely to have the same indention. This also makes sure that we don't have similar padding on the right-hand side, in case we change the text-size. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: use h2 instead of b-tag for headingsErik Faye-Lund2019-05-021-7/+11
| | | | | | | | <b>-tags aren't allowed in the root of <body>, so let's replace these with <h2>-tags with some CSS to make them appear as bold. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: remove stray paragraph-closeErik Faye-Lund2019-05-021-2/+0
| | | | | | | This tag tries to close a non-existent paragraph. Let's get rid of it! Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: properly escape ampersandErik Faye-Lund2019-05-022-2/+2
| | | | | | | | Even in preformatted blocks, ampersands should be escaped. Let's correct this, in case of strict parsers. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: properly escape '>'Erik Faye-Lund2019-05-022-5/+5
| | | | | | | | | The '>'-symbol should usually be escaped to avoid confusing strict parsers. While it's very unlikely to cause issues as-is, let's quite it for good measure. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: do not hard-code header-heightErik Faye-Lund2019-05-021-1/+1
| | | | | | | | | | | It's generally nicer to do this in terms of em units, as that scales better with text-sizes, if we ever decide to change them. The result is slightly larger than before, but only by a couple of pixels. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: simplify css-centeringErik Faye-Lund2019-05-021-4/+3
| | | | | | | | | With "display: flex;" we can make this a bit more automatic, not requiring a bunch of values to be of specific values to get the right centering. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: use multiple background-images for headerErik Faye-Lund2019-05-021-5/+2
| | | | | | | | This is a bit tidier than to set a background on the h1-text, requiring it to be full height and all. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: remove spurious newlineErik Faye-Lund2019-05-021-1/+0
| | | | | Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: avoid repeating the colorErik Faye-Lund2019-05-021-3/+0
| | | | | | | | The color attribute is inherited in CSS, so there's no point in repeating this. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: avoid repeating the fontErik Faye-Lund2019-05-021-2/+2
| | | | | | | | The font attribute is inherited in CSS, so there's no point in repeating this. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* docs: add missing semicolonErik Faye-Lund2019-05-021-1/+1
| | | | | | | | | While it's legal to omit the last semicolon in a CSS block, it's generally not considered good style, as it makes it harder to add new lines. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-29 04:37:28 +0000