* Bug with the website: links are broken
@ 2013-07-31 16:03 Chris R
2013-07-31 22:57 ` Luis R. Rodriguez
0 siblings, 1 reply; 6+ messages in thread
From: Chris R @ 2013-07-31 16:03 UTC (permalink / raw)
To: backports
I'm not sure who to report this to, but it is a problem for me. The links
for compat-wireless releases for 3.6 and earlier in this page:
http://wireless.kernel.org/en/users/Download/stable/
are broken. Can they please be fixed.
Thanks,
Chris
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Bug with the website: links are broken 2013-07-31 16:03 Bug with the website: links are broken Chris R @ 2013-07-31 22:57 ` Luis R. Rodriguez [not found] ` <007b01ce8eee$cca32e50$65e98af0$@gmail.com> 0 siblings, 1 reply; 6+ messages in thread From: Luis R. Rodriguez @ 2013-07-31 22:57 UTC (permalink / raw) To: Chris R; +Cc: backports@vger.kernel.org On Wed, Jul 31, 2013 at 9:03 AM, Chris R <chrisrfq@gmail.com> wrote: > I'm not sure who to report this to, but it is a problem for me. The links > for compat-wireless releases for 3.6 and earlier in this page: > > http://wireless.kernel.org/en/users/Download/stable/ > > are broken. Can they please be fixed. Its back up but that page has ancient releases, why are you still using them? The new temporary release page: http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/ Luis ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <007b01ce8eee$cca32e50$65e98af0$@gmail.com>]
* Re: Bug with the website: links are broken [not found] ` <007b01ce8eee$cca32e50$65e98af0$@gmail.com> @ 2013-08-01 19:43 ` Luis R. Rodriguez 2013-08-01 20:19 ` Hauke Mehrtens 2013-08-01 21:06 ` Chris R 0 siblings, 2 replies; 6+ messages in thread From: Luis R. Rodriguez @ 2013-08-01 19:43 UTC (permalink / raw) To: Chris R; +Cc: backports@vger.kernel.org On Thu, Aug 1, 2013 at 12:39 PM, Chris R <chrisrfq@gmail.com> wrote: >> Its back up... > > Thanks very much! > >> ...that page has ancient releases, why are you still using them? > > I'm stuck at kernel version 2.6.37. So backports is designed so that you use a backports-3.11 say on 2.6.37. That is you don't have to use a backport-3.10 only on 3.10 in fact that'd be pointless. We backport functionality from a kernel as a base and that base is used as the version name for the release. A few folks have reported misunderstanding this as well so I'm curious apart from the documentation we have on the wiki [0] what else can we do to help with this? [0] https://backports.wiki.kernel.org Luis ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bug with the website: links are broken 2013-08-01 19:43 ` Luis R. Rodriguez @ 2013-08-01 20:19 ` Hauke Mehrtens 2013-08-01 20:47 ` Luis R. Rodriguez 2013-08-01 21:06 ` Chris R 1 sibling, 1 reply; 6+ messages in thread From: Hauke Mehrtens @ 2013-08-01 20:19 UTC (permalink / raw) To: Luis R. Rodriguez; +Cc: Chris R, backports@vger.kernel.org On 08/01/2013 09:43 PM, Luis R. Rodriguez wrote: > On Thu, Aug 1, 2013 at 12:39 PM, Chris R <chrisrfq@gmail.com> wrote: >>> Its back up... >> >> Thanks very much! >> >>> ...that page has ancient releases, why are you still using them? >> >> I'm stuck at kernel version 2.6.37. > > So backports is designed so that you use a backports-3.11 say on > 2.6.37. That is you don't have to use a backport-3.10 only on 3.10 in > fact that'd be pointless. We backport functionality from a kernel as a > base and that base is used as the version name for the release. > > A few folks have reported misunderstanding this as well so I'm curious > apart from the documentation we have on the wiki [0] what else can we > do to help with this? > > [0] https://backports.wiki.kernel.org > > Luis Users do not read any documentation. ;-) I added it to multiple places in the wiki and still there are people in the IRC with such problems. We should make it fail if kernel version > backports version and we should also take the minor version into account. If the major version is the same we should print a big warning. Hauke ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bug with the website: links are broken 2013-08-01 20:19 ` Hauke Mehrtens @ 2013-08-01 20:47 ` Luis R. Rodriguez 0 siblings, 0 replies; 6+ messages in thread From: Luis R. Rodriguez @ 2013-08-01 20:47 UTC (permalink / raw) To: Hauke Mehrtens; +Cc: Chris R, backports@vger.kernel.org On Thu, Aug 1, 2013 at 1:19 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote: > Users do not read any documentation. ;-) > I added it to multiple places in the wiki and still there are people in > the IRC with such problems. > > We should make it fail if kernel version > backports version and we > should also take the minor version into account. If the major version is > the same we should print a big warning. I like the idea :D Luis ^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Bug with the website: links are broken 2013-08-01 19:43 ` Luis R. Rodriguez 2013-08-01 20:19 ` Hauke Mehrtens @ 2013-08-01 21:06 ` Chris R 1 sibling, 0 replies; 6+ messages in thread From: Chris R @ 2013-08-01 21:06 UTC (permalink / raw) To: 'Luis R. Rodriguez'; +Cc: backports > what else can we do to help with this? Two suggestions come to mind... 1. Don't number releases so they look like they correspond to kernel numbers, which implies a need to match. 2. Give an example such as: "In other words, use the current v3.10 release whether you are building for kernel 2.6.32 or 3.10" Sorry, but although English is my first and preferred language, it can still be deceptively ambiguous. How 'bout the following text: Backports is an effort to make sure that drivers that are released on the newest kernel are also the preferred drivers for use with older kernels. In other words, you can always use the latest stable backports release, even on older kernels. The backports drivers are usable back to kernel 2.6.32. ...or something like that. Whatever the oldest supported kernel is. Thanks for hitting me up-side the head! - Chris -----Original Message----- From: mcgrof@gmail.com [mailto:mcgrof@gmail.com] On Behalf Of Luis R. Rodriguez Sent: Thursday, August 01, 2013 12:44 PM To: Chris R Cc: backports@vger.kernel.org Subject: Re: Bug with the website: links are broken On Thu, Aug 1, 2013 at 12:39 PM, Chris R <chrisrfq@gmail.com> wrote: >> Its back up... > > Thanks very much! > >> ...that page has ancient releases, why are you still using them? > > I'm stuck at kernel version 2.6.37. So backports is designed so that you use a backports-3.11 say on 2.6.37. That is you don't have to use a backport-3.10 only on 3.10 in fact that'd be pointless. We backport functionality from a kernel as a base and that base is used as the version name for the release. A few folks have reported misunderstanding this as well so I'm curious apart from the documentation we have on the wiki [0] what else can we do to help with this? [0] https://backports.wiki.kernel.org Luis ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-08-01 21:07 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-31 16:03 Bug with the website: links are broken Chris R
2013-07-31 22:57 ` Luis R. Rodriguez
[not found] ` <007b01ce8eee$cca32e50$65e98af0$@gmail.com>
2013-08-01 19:43 ` Luis R. Rodriguez
2013-08-01 20:19 ` Hauke Mehrtens
2013-08-01 20:47 ` Luis R. Rodriguez
2013-08-01 21:06 ` Chris R
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).