From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] tcp problem
Date: Wed, 21 May 2008 08:01:22 -0400 [thread overview]
Message-ID: <103c6138905e9c7fb11cc4985dd7c23e@9srv.net> (raw)
In-Reply-To: <d7ae9c9b008e172e68d1b40d2a0f5f74@quintile.net>
// If this fails you probably need to add the line
// "srv fossil" to your fossil config (using fossil/conf);
// See fossil(1).
I think "listen" and fossilcons(8) are more likely to be
helpful (although fossil(1) should get you there, if
indirectly).
Incidentally, I read the subject line as a declarative,
sort of an equivalency, and thought "couldn't agree
more; I want nonet back!). ☺
Anthony
next prev parent reply other threads:[~2008-05-21 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 8:58 lupin636
2008-05-21 9:23 ` Steve Simon
2008-05-21 12:01 ` a [this message]
2008-05-23 8:36 ` lupin636
2008-05-23 9:50 ` Christian Kellermann
2008-05-23 17:20 ` a
2008-05-27 9:08 ` lupin636
2008-05-27 9:08 ` lupin636
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=103c6138905e9c7fb11cc4985dd7c23e@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).