From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37430
Path: main.gmane.org!not-for-mail
From: Simon Josefsson <jas@extundo.com>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: Backend writing
Date: Fri, 03 Aug 2001 23:44:46 +0200
Message-ID: <iluelqsx1gx.fsf@barbar.josefsson.org>
References: <suse-7.0-professional.m2hevpaulk.fsf@tcob1.net>
	<m33d79c4pm.fsf@multivac.cwru.edu>
	<vafg0b8kgjm.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: main.gmane.org 1035172847 13838 80.91.224.250 (21 Oct 2002 04:00:47 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 04:00:47 +0000 (UTC)
Cc: ding@gnus.org
Return-Path: <jas@barbar.josefsson.org>
Return-Path: <jas@barbar.josefsson.org>
Original-Received: (qmail 26190 invoked from network); 3 Aug 2001 21:43:28 -0000
Original-Received: from slipsten.extundo.com (HELO barbar.josefsson.org) (195.42.214.241)
  by gnus.org with SMTP; 3 Aug 2001 21:43:28 -0000
Original-Received: (from jas@localhost)
	by barbar.josefsson.org (8.11.2/8.11.2) id f73LilA01985;
	Fri, 3 Aug 2001 23:44:47 +0200
Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=)
In-Reply-To: <vafg0b8kgjm.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
 (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 Aug 2001
 22:57:33 +0200")
Mail-Copies-To: nobody
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Artificial
 Intelligence)
Original-Lines: 17
Xref: main.gmane.org gmane.emacs.gnus.general:37430
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37430

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

>| that number, or Gnus will get mightily confused.@footnote{??? Is this
>| still true with the nnchoke-request-*-mark* functions?}  Third, article

It's still true.

>| The previous paragraph already mentions all the `hard' restrictions that
>| article numbers must fulfill.  But it seems that it might be useful to
>| assign @emph{consecutive} article numbers, for Gnus gets quite confused
>| if there are holes in the article numbering sequence.  However, due to
>| the `no-reuse' restriction, holes cannot be avoided altogether.

I would say "is slowed down" instead of "gets quite confused".  I
don't think there are any problems, other than that the `gnus-range-*'
functions start to take very long time.  Some IMAP servers leave large
holes.