From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb version 3.7 in kernel 2.4.20?
Date: Thu, 12 Dec 2002 18:35:30 +0000 [thread overview]
Message-ID: <marc-lartc-103971833016516@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103970026925933@msgid-missing>
Bug fixes only. Think about it like 3.6 was beta and 3.7 is final.
On Thu, 12 Dec 2002, Julio E. Gonzalez P. wrote:
> When you use HTB with a stock linux kernel 2.4.20, in /var/log/messages
> say it is version 3.7.
> Anyone know something about this?
> The HTB home page only mentions HTB version 3.6.
> What changes it have?
>
> Julio.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-12 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 13:32 [LARTC] htb version 3.7 in kernel 2.4.20? Julio E. Gonzalez P.
2002-12-12 18:13 ` Stef Coene
2002-12-12 18:35 ` Martin Devera [this message]
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=marc-lartc-103971833016516@msgid-missing \
--to=devik@cdi.cz \
--cc=lartc@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox