From: David Collier-Brown <davec-b@rogers.com>
To: Dave Taht <dave.taht@gmail.com>,
David Collier-Brown <davecb@spamcop.net>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] missing part of section 6.2 of draft-nichols-tsvwg-codel-02, (Kathleen Nichols)
Date: Wed, 12 Mar 2014 17:32:58 -0400 [thread overview]
Message-ID: <5320D28A.7070100@rogers.com> (raw)
In-Reply-To: <CAA93jw4kp9ChCaybjbVQ17zO_zO18ecS8O4G53StieV0HtBDXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On 03/12/2014 04:23 PM, Dave Taht wrote:
>
>
> On Mar 12, 2014 1:11 PM, "David Collier-Brown" <davec-b@rogers.com
> <mailto:davec-b@rogers.com>> wrote:
> >
> > [Off-topic]
> > Someone with classic-typesetting-tools experience might wish to
> > volunteer a pandoc-based process. See, for example,
> > http://lwn.net/SubscriberLink/589196/0e8f212d7a59f556/
>
> The fq codel rfc was written in pandoc, and converted via pandoc2rfc.
> The raw texts are managed in git and in github.
>
> It took me a year of fiddling to get to acceptable output from this.
>
> The amount of effort required was comparable to getting a paper
> formatted for the IEEE with TeX, with far less pleasing results than TeX.
>
> Certainly you have to be committed if you want to write an rfc. The
> present process is a major barrier to entry.
>
> >
> > --dave
>
AARGH!
I wasn't expecting that...
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 2229 bytes --]
next prev parent reply other threads:[~2014-03-12 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1394650801.32519.codel@lists.bufferbloat.net>
2014-03-12 20:11 ` David Collier-Brown
2014-03-12 20:23 ` Dave Taht
2014-03-12 21:32 ` David Collier-Brown [this message]
2014-03-13 8:32 ` Eggert, Lars
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5320D28A.7070100@rogers.com \
--to=davec-b@rogers.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=davecb@spamcop.net \
/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