From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Archives/Usenet server of Ding list
Date: Tue, 15 Mar 2011 10:52:39 -0500 [thread overview]
Message-ID: <877hc04bzs.fsf@lifelogs.com> (raw)
In-Reply-To: <m3oc5cl797.fsf@quimbies.gnus.org>
On Tue, 15 Mar 2011 16:43:00 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> David Kastrup <dak@gnu.org> writes:
>> The ding mailing list is gatewayed to the gnus.ding newsgroup. The
>> gateway is bi-directional everything mailed to the mailing list
>> will appear on the newsgroup, and all articles posted to the
>> newsgroup will appear on the mailing list.
>>
>> There is a hyperlink on gnus.ding leading to the appropriately named
>> group on the news.gnus.org server.
LMI> I've now updated this to point to the Gmane archive instead.
LMI> (At least I think I have -- Ted, does the automatic deployment work?
LMI> :-)
Not yet but this is a good chance to test it. I'll try it out soon-ish
and maybe do some trivial pushes to trigger the deployment.
Ted
next prev parent reply other threads:[~2011-03-15 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 15:26 David Kastrup
2011-03-15 15:43 ` Lars Magne Ingebrigtsen
2011-03-15 15:52 ` Ted Zlatanov [this message]
2011-03-17 11:22 ` Ted Zlatanov
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=877hc04bzs.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).