From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Chris R <chrisrfq@gmail.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Bug with the website: links are broken
Date: Thu, 01 Aug 2013 22:19:59 +0200 [thread overview]
Message-ID: <51FAC2EF.8080402@hauke-m.de> (raw)
In-Reply-To: <CAB=NE6Xg_MHwZAaZHHkL841BHJxFzEeu2oMZJdXpqYoGSHjSgQ@mail.gmail.com>
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
next prev parent reply other threads:[~2013-08-01 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-08-01 20:47 ` Luis R. Rodriguez
2013-08-01 21:06 ` Chris R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51FAC2EF.8080402@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=chrisrfq@gmail.com \
--cc=mcgrof@do-not-panic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.