From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Picon questions
Date: Sun, 13 Jan 2002 16:46:48 +1100 [thread overview]
Message-ID: <87lmf2reev.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <vxk7kqnfkv6.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Sat, 12 Jan 2002 14:08:13 -0500")
On Sat, 12 Jan 2002, Karl Kleinpaste wrote:
[...]
> Also, it seems to me that, once people have picked up the picon
> *.tar.Z files, they'll never again get them (they're huge).
Aren't they?
> Is there any sort of auto-update scheme, I suppose in a subscription
> motif, where one could be notified of new picons' availability?
Not that I was ever able to find. The Debian maintainer of the picons
does a fairly infrequent update of the packages...
...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. :)
Daniel
--
Nature provides a free lunch, but only if we control our appetites.
-- William Ruckelshaus, _Business Week_, 18 June 1990
next prev parent reply other threads:[~2002-01-13 5:46 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 [this message]
2002-01-19 22:11 ` Lars Magne Ingebrigtsen
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=87lmf2reev.fsf@inanna.rimspace.net \
--to=daniel@rimspace.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).