netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "martin f. krafft" <madduck@madduck.net>
To: netdev@vger.kernel.org
Subject: Re: Netconf at conf.au 2008?
Date: Mon, 14 Jan 2008 11:13:58 +0100	[thread overview]
Message-ID: <20080114101358.GA24498@lapse.madduck.net> (raw)
In-Reply-To: <20080113.181227.67682894.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

also sprach David Miller <davem@davemloft.net> [2008.01.14.0312 +0100]:
> > I think you may be mixing things up, and it may be my fault in
> > ways. I am developing netconf: http://netconf.alioth.debian.org.
> > I am aware of the NETCONF protocol and have considered renaming
> > my project, but looking around, it seemed to me that NETCONF
> > isn't really all that active, and so I chose to keep the name.
> > If people think that wasn't wise, I'm willing to listen...
> 
> Netconf is the name of the usually annual conference the core
> Linux networking developer organize.

Fun fun fun: name clashes. In Debian, we have debconf, the tool, the
protocol and the conference. Now we have netconf, the tool, the
protocol and the conference.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
if you find a spelling mistake in the above, you get to keep it.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-14 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12  6:52 Netconf at conf.au 2008? Andy Johnson
2008-01-13 14:53 ` Glen Turner
2008-01-14  2:08   ` David Miller
2008-01-14  8:34     ` Andy Johnson
2008-01-14 11:01     ` Glen Turner
2008-01-14 11:57       ` David Miller
2008-01-13 18:17 ` martin f krafft
2008-01-14  2:12   ` David Miller
2008-01-14 10:13     ` martin f. krafft [this message]
2008-01-14 11:06   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-14 16:39     ` martin f. krafft

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=20080114101358.GA24498@lapse.madduck.net \
    --to=madduck@madduck.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).