From: Daniel Bergqvist daniel@netatonce.se
To: lartc@vger.kernel.org
Subject: [LARTC] TC command reference
Date: Wed, 06 Dec 2000 10:35:25 +0000 [thread overview]
Message-ID: <marc-lartc-98373938217007@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216968@msgid-missing>
<PRE>><i>Från: <A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A> [mailto:<A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A>]För
</I>bert hubert
><i>Skickat: Wednesday, December 06, 2000 11:54 AM
</I>>><i> I have now added most of the options to the qdiscs and filters and I have
</I>>><i> converted the source to DocBook SGML. Where are still parts missing but
</I>I'm
>><i> working on it.
</I>><i>
</I>>><i> The address is: <A HREF="http://linux.bergqvist.se/tc/">http://linux.bergqvist.se/tc/</A>
</I>><i>
</I>><i>The beginnings look good. It might be an idea to have your document stick
</I>to
><i>explaining the syntax, and having the terminology explained in the Advanced
</I>><i>Routing & Shaping HOWTO?
</I>Yes, it seems good.
>><i> I have a couple of questions:
</I>>><i>
</I>>><i> * How is it with other documentation about TC? For example the
</I>documentation
>><i> Alex Goldney is working on? Then I started this there was almost none,
</I>but
>><i> it seems several people are working on TC documentation and there is no
</I>>><i> reason for me to document things that others are working on.
</I>><i>
</I>><i>We should unify the efforts and possibly persuade Alexey to bundle your and
</I>><i>others' works with iproute2.
</I>Good.
><i>Regards,
</I>><i>
</I>><i>bert hubert
</I>
Regards,
Daniel
</PRE>
next prev parent reply other threads:[~2000-12-06 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 14:38 [LARTC] TC command reference Daniel
2000-12-06 9:53 ` Daniel
2000-12-06 10:35 ` Daniel [this message]
2000-12-06 10:54 ` bert
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-98373938217007@msgid-missing \
--to=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 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.