From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/38294 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: self-contained nnml Date: Sat, 25 Aug 2001 11:43:40 +0200 Message-ID: References: <87wv3tqd1q.fsf@raven.i.defaultvalue.org> <87lmk90z3w.fsf@raven.i.defaultvalue.org> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035174181 21593 80.91.224.250 (21 Oct 2002 04:23:01 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:23:01 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 17471 invoked from network); 25 Aug 2001 09:43:54 -0000 Original-Received: from dolk.extundo.com (195.42.214.242) by gnus.org with SMTP; 25 Aug 2001 09:43:54 -0000 Original-Received: from barbar.josefsson.org (slipsten.extundo.com [195.42.214.241]) (authenticated) by dolk.extundo.com (8.11.6/8.11.6) with ESMTP id f7P9hrh09433; Sat, 25 Aug 2001 11:43:53 +0200 Original-To: Rob Browning In-Reply-To: <87lmk90z3w.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Fri, 24 Aug 2001 19:20:19 -0500") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104 Original-Lines: 27 Xref: main.gmane.org gmane.emacs.gnus.general:38294 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:38294 Rob Browning writes: >> So does this also apply for a group within a server? i.e. could I "B >> m" a bunch of articles from nnml+rlb:ding-gnus to >> nnml+rlb:ding-gnus-2000 and then tar up and remove the ding-gnus-2000 >> directory without seriously confusing gnus? Similarly could I restore >> the group by dropping it back into place in the filesystem? > > OK. After looking at what happens (now that I've upgraded to Oort), I > can see that the .marks are per-group. It also mentions that it's > per-group in GNUS-NEWS. Now I'll just have to see how happy Gnus is > with removals and restores. Remember that the active file is per server. I think nnml automatically regenerates active info for new groups though. Just don't untar it in directory that already have a active entry. Please do test this, I'm not aware of anyone that actually _used_ it. The per-server active file could go into a per-group .active file, but we'd might as well remove the active file completely. Nnml could store this info in a lisp variable. To populate it when Gnus boots it could look at first/last line of .overview at startup. I don't think the active file contains any information not efficiently available by other methods. Then we would have self-contained nnml groups. Group level and group parameters are not store stored in the nnml directory though.