From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Picon questions
Date: Sat, 19 Jan 2002 23:11:55 +0100 [thread overview]
Message-ID: <m3zo3ang7o.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87lmf2reev.fsf@inanna.rimspace.net>
Daniel Pittman <daniel@rimspace.net> writes:
> ...but if someone with a large amount of (free) bandwidth was to set up
> an rsync server or something like that which people could update from,
> that would be very nice. :)
The problem with the picons is that they aren't free, so that would
have to be OK'd by the picons maintainer personages.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-01-19 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 19:08 Karl Kleinpaste
2002-01-12 19:26 ` Lars Magne Ingebrigtsen
2002-01-13 5:46 ` Daniel Pittman
2002-01-19 22:11 ` Lars Magne Ingebrigtsen [this message]
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=m3zo3ang7o.fsf@quimbies.gnus.org \
--to=larsi@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).