[gentoo-commits] proj/linux-patches:genpatches-misc commit in: web/content/

[Mike Pagano]

commit:     bda1c0fd63033829ea7e50376ec74c9056f3c7d6
Author:     Mike Pagano <mpagano <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 30 11:11:36 2018 +0000
Commit:     Mike Pagano <mpagano <AT> gentoo <DOT> org>
CommitDate: Fri Mar 30 11:11:36 2018 +0000
URL:        https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=bda1c0fd

Rename htm files to html

 web/content/about.html   | 75 ++++++++++++++++++++++++++++++++++++++++++++++++
 web/content/bugs.html    | 47 ++++++++++++++++++++++++++++++
 web/content/nav.html     | 10 +++++++
 web/content/sitemap.html | 51 ++++++++++++++++++++++++++++++++
 4 files changed, 183 insertions(+)

diff --git a/web/content/about.html b/web/content/about.html
new file mode 100644
index 0000000..5e63ad6
--- /dev/null
+++ b/web/content/about.html
@@ -0,0 +1,75 @@
+<h2>What is genpatches?</h2>
+
+<p>
+genpatches is a patchset applied to many of Gentoo's Linux kernel packages. It
+aims to support the entire range of Gentoo-supported architectures.
+</p>
+
+<p>
+Each patchset is based on the initial stable release of the kernel's released at
+kernel.org (e.g. 2.6.10, 2.6.11, 2.6.12). 
+</p>
+
+<p>
+The patchset is split up into two parts: base and extras. base contains bug and
+security fixes, while extras includes some extra hardware support and some
+feature patches.
+</p>
+
+<p>
+genpatches is mainly produced for <b>gentoo-sources</b>, which is the only
+kernel to include both base and extras.
+</p>
+
+<p>
+genpatches is maintained in Gentoo Git. This is <a href="https://gitweb.gentoo.org/proj/linux-patches.git/">browseable online</a> and the trunk contents are regularly mirrored <a href="trunk/">here</a>.
+</p>
+
+<p>
+genpatches releases are announced on the gentoo-kernel mailing list. To subscribe, send a mail to <a href="mailto:gentoo-kernel+subscribe@l.g.o">gentoo-kernel+subscribe@l.g.o</a>. The list is very low traffic, almost all mails are genpatches release announcements. You can also view the <a href="http://archives.gentoo.org/gentoo-kernel/">list archives</a>.
+</p>
+
+<p>
+genpatches is not specific to Gentoo at all, it can be viewed as a general purpose Linux patchset focusing on stability. Some other non-Gentoo projects use genpatches too, and that's great. If you want to use genpatches in your distro/project, please feel free, and do let me know.
+</p>
+
+<p>
+More information can be found in the <a href="faq.htm">FAQ</a>.
+</p>
+
+<h2>Patching policy</h2>
+
+<p>
+We aim to keep genpatches as a minimal patchset for two reasons:
+</p>
+
+<ol><li>Ease of maintenance and debugging</li>
+<li>Minimal deviation from upstream releases</li></ol>
+
+The second point being the most important - we don't want to bloat our kernel and turn it into a stability and maintenance nightmare. We also want to be able to easily update our base to new stable kernel releases soon after they appear.
+
+With that in mind, here are the types of patches that we include:<br />
+<ol>
+<li>Bug fixes</li>
+<li>Security fixes</li>
+<li>Arch-specific compatibility</li>
+<li>Features required or beneficial for Gentoo LiveCDs</li>
+</ol>
+
+<p>
+In general, we try to stick to only applying patches from the upstream Linux development branch. We're not opposed to fancy new features, we just feel that they belong only in the official kernel.org releases so that every Linux distribution can benefit.
+</p>
+
+<h2>Roadmap</h2>
+
+<p>
+For now we are just working on each new kernel release, adding upstream patches to solve any problems that have appeared, while keeping up-to-date with the kernel.org stable releases.
+</p>
+
+<p>
+We also aim to increase the number of Gentoo-provided kernels which include
+genpatches-base. This greatly reduces the maintenance of those other kernels
+since all security patch handling is done in one place only.
+</p>
+
+

diff --git a/web/content/bugs.html b/web/content/bugs.html
new file mode 100644
index 0000000..f411a9d
--- /dev/null
+++ b/web/content/bugs.html
@@ -0,0 +1,47 @@
+<h2>If you are having problems with the gentoo-sources kernel</h2>
+You may find the process being described below a bit long-winded, and you may decide to skip some steps. However, once you file a bug report, we may ask you to do some steps you have skipped, depending on the information we need. Interpret the following as <i>the perfect way to report a kernel bug!</i>
+
+<ol>
+
+<li><b><a href="issues.htm">Check the issues & solutions page first!</a></b> Chances are that we are aware of the problem and have already provided a solution.</li>
+<br />
+
+<li><b>Make sure you are running the latest release,</b> and if you aren't, upgrade and check that the issue hasn't already been fixed. This may involve you <a href="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3#doc_chap2">going into the testing tree</a>:
+<blockquote><pre>mkdir -p /etc/portage
+echo "sys-kernel/gentoo-sources" >> /etc/portage/package.keywords
+emerge -up gentoo-sources</pre></blockquote></li>
+<br />
+
+<li><b>If you compiled your kernel with "make oldconfig"</b>, then clear your .config and manually configure it all again. You'd be suprised at how many problems this fixes. Sometimes it is user error, sometimes it is just oddities with the kernel build system. I personally don't like "make oldconfig".</li>
+<br />
+
+<li><b>Attempt to reproduce the problem on the equivalent stable "vanilla" kernel release</b>. For example, if you are having the problem with gentoo-sources-2.6.9-r3, then you should try to reproduce the problem on development-sources-2.6.9. This helps us to narrow down whether the problem is introduced by the gentoo patchset, or if it exists in the upstream kernel that we are based on.<br /><br />
+
+<b>If the problem is present in the stable vanilla release</b>, then attempt to reproduce the problem on the newest release candidate vanilla kernel (if there is one). In the above example, you would now go on to test and see if the issue is still present in development-sources-2.6.10-rc1 (assuming -rc1 is the latest release candidate).
+
+</li>
+<br />
+
+<li><b>Research your problem</b> on our <a href="http://bugs.gentoo.org">bugzilla</a> and <a href="http://forums.gentoo.org">forums</a>. If you think its appropriate, you may also wish to try searching on <a href="http://www.google.com">Google<a> and <a href="http://bugzilla.kernel.org">the central kernel bugzilla</a>. Maybe someone else has provided a solution - even if this is the case, please continue on to filing a bug, we'd like to hear about it.</li>
+
+<br />
+
+<li><b>In the previous step, if you found that someone else has already reported the bug on our bugzilla</b>, then please add yourself to the CC list of that bug and post a comment saying that you have the same problem, and add any information you have gathered from the above steps. Otherwise, carry on to the next step.</li>
+<br />
+
+<li><b><a href="http://bugs.gentoo.org/enter_bug.cgi?format=guided">File a bug on our bugzilla</a></b></b>. Describe your problem in full, and detail the results of the steps you have performed above. Include obvious details such as which kernels are affected by the problem, and paste the output from "emerge info" where asked.<br /><br />
+If you think it is relevant, you may wish to post your .config file and the output of "dmesg". <b>Please do not paste these in the Details box</b>, but instead, post them as a <b>text/plain</b> attachment after you have submitted the bug report.</li>
+
+<br />
+
+<li><b>Wait for a response from a developer</b>. We're busy people, we might not always be very quick at responding. If we do request more info, please provide it as soon as you can.<br /><br />
+
+If you had deduced in the previous steps that this issue is present in the latest release-candidate kernel, then we may close the bug, asking you to post a bug report at the upstream <a href="http://bugzilla.kernel.org">central kernel bugzilla</a>. Don't be offended by this - we are interested in solving the problem, but its not always on our territory. However we do prefer to hear about issues users are having, and you will have fulfilled this by filing the bug with us first.<br /><br />
+
+If we have asked you to file the bug upstream, then please check that nobody else has already reported it there. In your report, be sure to mention that the problem exists on the plain kernels from kernel.org, rather than only saying the problem is experienced on the Gentoo kernel.<br /><br />
+
+Once you have posted the upstream bug, please return to the Gentoo bug and update the URL field with the URL of the upstream bug report. Once the bug has been solved with the upstream developer, please post a new comment on the Gentoo bug informing us of this, and we'll consider (where appropriate) importing the fix into gentoo-sources.</li>
+
+</ol>
+
+Finally, thanks for your co-operation! By doing the above, you will have helped anyone else with the same issue, and if you identified and helped solve a core kernel issue then the entire Linux community will have benefitted out of your efforts. Although its very easy to ignore bugs hoping that they will be fixed for the next release, *someone* needs to report them for them to be fixed.

diff --git a/web/content/nav.html b/web/content/nav.html
new file mode 100644
index 0000000..94d1fa6
--- /dev/null
+++ b/web/content/nav.html
@@ -0,0 +1,10 @@
+<table cellpadding="1" cellspacing="3" border="0" bgcolor="lightgrey" class="menu">
+<tr>
+<td class="menu"><a href="index.htm">Home</a></td>
+<td class="menu"><a href="about.htm">About</a></td>
+<td class="menu"><a href="faq.htm">FAQ</a></td>
+<td class="menu"><a href="releases.htm">Releases</a></td>
+<td class="menu"><a href="bugs.htm">Bugs</a></td>
+<td class="menu"><a href="issues.htm">Issues</a></td>
+</tr>
+</table>

diff --git a/web/content/sitemap.html b/web/content/sitemap.html
new file mode 100644
index 0000000..4bc5a0e
--- /dev/null
+++ b/web/content/sitemap.html
@@ -0,0 +1,51 @@
+<h1>genpatches homepage</h2>
+
+<h2>Information</h2>
+
+<ul>
+
+<li><b><a href="about.htm"><h4>About genpatches</h4></a></b><br />
+A brief description of the package, and details about our patching and release policy.</li>
+
+<li><b><a href="kernels.htm"><h4>Available Kernels</h4></a></b><br />
+List of kernels available in Portage which are based on genpatches.</li>
+
+<li><b><a href="faq.htm"><h4>Frequently Asked Questions</h4></a></b><br />
+Questions that we are bored of answering :)</li>
+
+<li><b><a href="releases.htm"><h4>Release Information</h4></a></b><br />
+Information about the patches we apply to our kernel releases, and links to patch tarballs.</li>
+
+<li><b><a href="bugs.htm"><h4>Reporting Bugs</h4></a></b><br />
+The ideal process you should follow when reporting kernel bugs.</li>
+
+<li><b><a href="issues.htm"><h4>Known Issues &amp; Solutions</h4></a></b><br />
+Details about common issues with our kernel releases, and their solutions.</li>
+
+</ul>
+
+<h2>Resources</h2>
+
+<ul>
+
+<li><b><a href="trunk/"><h4>Trunk</h4></a></b>
+Latest split-out patches from our current development trees, viewable on the web.</li>
+<br/>
+
+<li><b><a href="tarballs/"><h4>Tarballs</h4></a></b>
+An archive of all the release tarballs.</li>
+<br/>
+
+<li><b><a href="http://git.gentoo.org/gitweb/?p=proj/linux-patches.git;a=summary"><h4>Repository</h4></a></b>
+The entire repository and its history is browseable here.</li>
+<br/>
+
+<li><b><a href="http://bugs.gentoo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=kernel%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0="><h4>Gentoo Kernel Bugs</h4></a></b>
+Gentoo's current kernel bug list.</li>
+<br/>
+
+<li><b><a href="http://bugzilla.kernel.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&kernel_version_type=allwordssubstr&kernel_version=&bug_status=NEW&bug_status=ASSIGNED&emailcc1=1&emailtype1=substring&email1=kernel%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0="><h4>Gentoo Upstream Kernel Bugs</h4></a></b>
+Problems reported by Gentoo users regarding the mainline kernel, currently being tracked.</li>
+<br/>
+
+</ul>