netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: david-b@pacbell.net
Cc: rddunlap@osdl.org, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: netlink tester program
Date: Mon, 02 Jun 2003 20:38:34 -0700 (PDT)	[thread overview]
Message-ID: <20030602.203834.115933659.davem@redhat.com> (raw)
In-Reply-To: <3EDC173B.80909@pacbell.net>

   From: David Brownell <david-b@pacbell.net>
   Date: Mon, 02 Jun 2003 20:34:19 -0700

   > See, a document is NOT the spec, the code is the spec.
   
   That's hardly the only development model.
   
It's the one that works for _me_ and Alexey and myself, and we're the
ones doing all the work.

When someone doing the work desires the docs and desires to
WRITE it, it will appear.
   
You can expect exactly nothing more in our development model.
If you require me to write the docs, you misunderstand how the
system works :)

   You clipped out the text where I pointed out that bugs can
   be in specs as well as code.  They can be fixed there, too.
   
Very true.  So when Randy writes the more detailed netlink/rtnetlink
docs, we'll be happy :-)
   
There is even an official IETF RFC written by Jamal, Alexey, and
others documenting netlink btw :-))))))))))))

Did anybody notice this?

  reply	other threads:[~2003-06-03  3:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 16:00 netlink tester program Randy.Dunlap
2003-05-31  0:11 ` David S. Miller
2003-05-31  3:22   ` Randy.Dunlap
2003-05-31  6:42     ` David S. Miller
2003-05-31 12:09       ` Andi Kleen
2003-06-02 17:07         ` Randy.Dunlap
2003-06-02 21:04       ` Randy.Dunlap
2003-06-02 21:56         ` David S. Miller
2003-06-03  1:56           ` David Brownell
2003-06-03  2:02             ` David S. Miller
2003-06-03  3:34               ` David Brownell
2003-06-03  3:38                 ` David S. Miller [this message]
2003-06-03  3:49                   ` Randy.Dunlap
2003-06-03  3:51                     ` David S. Miller
2003-06-03  7:57                   ` Hisham Kotry
2003-06-09  1:35                     ` Jamal Hadi
2003-06-09 14:37                       ` Mr. James W. Laferriere
2003-06-09 17:16                       ` David S. Miller
2003-06-03  2:33           ` John S. Denker
2003-06-03  2:38             ` David S. Miller
2003-06-03  3:20               ` John S. Denker
2003-06-03  3:22                 ` David S. Miller
2003-06-03  3:41                   ` John S. Denker
2003-06-03  3:46                     ` David S. Miller
2003-06-03  3:54                       ` Randy.Dunlap
2003-06-03  3:54                         ` David S. Miller
2003-06-03  3:37             ` David Brownell
2003-06-03  3:32           ` Randy.Dunlap
2003-06-03  3:35             ` David S. Miller

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=20030602.203834.115933659.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).