From: albrecht@vlsivie.tuwien.ac.at (Albrecht Kadlec)
Cc: ding@ifi.uio.no
Subject: Re: How to move saved articles to cache?
Date: 18 Mar 1996 14:14:59 +0100 [thread overview]
Message-ID: <tispf6sfu3.fsf@java.vlsivie.tuwien.ac.at> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 11 Mar 1996 20:54:37 +0100
>>>>> Lars Magne Ingebrigtsen writes:
L> albrecht@vlsivie.tuwien.ac.at. (Albrecht Kadlec) writes:
> Any way to have gnus save a bunch of articles under "very low", unused
> article numbers (to move old saved articles into the cache) ?
L> Not automatically, no.
> I was wondering what my cache will turn to, when I move (to another News
> server) ? - all screwed up ? (shiver)
L> Yes, sort of. The article numbers in the cache should be the same as
L> the article numbers from the server.
> I just imagine the new news server to use article numbers minus
> 1000. Will all my cached articles be replaced, will I never see the
> 'conflicting' new ones, if I simply copy my cache hierarchy?
L> You won't see conflicting new ones. You could just renumber the files
L> to be lower than the articles on the new server, though. Perhaps
L> there should be a function to do something like that --
L> gnus-renumber-cache' or something.
(gnus-reallocate-cache-numbers) ?
renumber according to message ID,
(fetch ID from saved article, ask server for its number)
if the server doesn't have this one, allocate it REAL LOW
i.e: maybe starting from 1
I don't know if it's efficient, but it'd be smoothest for the user.
anyway,
added to the RED to-do ?
just asking,
albrecht
prev parent reply other threads:[~1996-03-18 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-09 13:49 John Griffith
1996-03-09 22:56 ` Lars Magne Ingebrigtsen
1996-03-11 10:15 ` Albrecht Kadlec
1996-03-11 19:54 ` Lars Magne Ingebrigtsen
1996-03-18 13:14 ` Albrecht Kadlec [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=tispf6sfu3.fsf@java.vlsivie.tuwien.ac.at \
--to=albrecht@vlsivie.tuwien.ac.at \
--cc=albrecht@auto.tuwien.ac.at \
--cc=ding@ifi.uio.no \
/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).