Gnus development mailing list
 help / color / mirror / Atom feed
From: David Moore <dmoore@UCSD.EDU>
Subject: Re: Discussion: To del cached articles upon zapping group info?
Date: 08 Nov 1996 17:17:50 -0800	[thread overview]
Message-ID: <rvsp6khxs1.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 08 Nov 1996 15:17:04 +0100

Wesley.Hardaker@sphys.unil.ch writes:
> I said it should delete the cached articles, simply because they are
> no longer valid and will conflict with new numbered articles.  There
> is simply no place in the 1-* range for them as they have been taken
> up by new numbers.

	Well, it certainly shouldn't delete them, although you want it
to stick them into some other archive kind of group.  You probably
cached them because they had useful information.  But you obviously
can't leave them in the cache tree, since they conflict with other
messages.  You could probably roll your old articles into an archive,
set the new real newsgroup to a highish level, and drop a virtual group
on top of them to combine them.  Although this isn't a great solution.

> I suppose you could re-order them to something like -3 -> -1 or
> something similar, but I don't know how gnus would handle that (this
> is a new idea Lars).

I kindof like that idea.  Of course a couple places in the code, it
explicitly checks for negative numbers in ranges and removes them.

	When I have to change news servers, which may happen some day,
I'd like to keep my cache as enties in the same ''group'' without it
overriding other potential articles, and also not being a seperate
entity.

-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | Solo Furnace Creek 508 -- 1996!


  reply	other threads:[~1996-11-09  1:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-08 14:17 Wesley.Hardaker
1996-11-09  1:17 ` David Moore [this message]
1996-11-09  2:59   ` Lars Magne Ingebrigtsen
1996-11-13 10:02     ` Wesley.Hardaker
1996-11-13 16:50       ` Edward J. Sabol
1996-11-13 18:21         ` David Moore
1996-11-14  7:20           ` Wesley.Hardaker
1996-11-14  9:01           ` Lars Magne Ingebrigtsen
1996-11-14  9:26             ` Per Abrahamsen
1996-11-14 13:32               ` Wesley.Hardaker
1996-11-15 21:53                 ` Lars Magne Ingebrigtsen
1996-11-15 22:12                 ` Paul Franklin
1996-11-16 18:23                   ` 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=rvsp6khxs1.fsf@sdnp5.ucsd.edu \
    --to=dmoore@ucsd.edu \
    /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).