From: Jeremy Kerr <jk@ozlabs.org>
To: netfilter-devel@lists.netfilter.org
Cc: Harald Welte <laforge@netfilter.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: nfsim updates
Date: Wed, 22 Sep 2004 21:04:36 -0400 [thread overview]
Message-ID: <200409222104.36526.jk@ozlabs.org> (raw)
In-Reply-To: <1095732625.1940.166.camel@bach>
> > As stated before, we could also move it to
> > svn.netfilter.org (which actually exists, but also has no public
> > interface yet).
>
> Jeremy?
This would probably be the best way to go - It also depends on how the
netfilter testsuite is going to be developed - would using the subversion
repository cause any problems, rather than rolling it into netfilter cvs?
In the meantime though, I've set up a cron task to create a nightly snapshot
from the ozlabs.org subversion repository (23:00 AEST). This puts the .tar.gz
up at:
http://ozlabs.org/~jk/projects/nfsim/
Jeremy
next prev parent reply other threads:[~2004-09-23 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 22:34 nfsim updates Harald Welte
2004-09-21 2:13 ` Rusty Russell
2004-09-23 1:04 ` Jeremy Kerr [this message]
2004-09-23 12:41 ` Eric Leblond
2004-09-25 7:00 ` Harald Welte
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=200409222104.36526.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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.