zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: List archive not tracking new home site?
Date: 28 Jan 1999 03:38:06 GMT	[thread overview]
Message-ID: <slrn7avmsu.1br.mason@coral.primenet.com.au> (raw)
In-Reply-To: <yd8lnioob29.fsf@zastava.kom.auc.dk>

Karsten Thygesen <karthy@kom.auc.dk> typed:
[...my comments deleted...]
:That could be done, but when people subscribe or unsubscribe, the
:message must go to sunsite.auc.dk, and that is not very intuitive and
:I fear a lot of people will try to do administrative changes by
:posting to the main lists.

I can set up
  users-anythingblah@zsh.org to go to zsh-users-anythingblah@zsh.org
and others in about 60-70 seconds.

:Also, ezmlm keeps track of who is missing
:what messages, and if a message bounce due to temporary errors, it
:will notify the receiver about which messages he is messing - these
:messages will be numbered in the ezmlm-scheme.

There are also questions on what are the current "official" numbers:
	Date: 28 Jan 1999 09:29:09 +1100
	Message-ID: <slrn7av4lh.d2q.dave@jagor.srce.hr>
	X-Seq: 5069
	X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/4970
The message went through both gatech and sunsite.auc so picked up two sets
of numbers.  Neither is more useful than the other.  gatech is now missing
messages that get sent straight to sunsite.auc.  sunsite.auc has announce
and users messages mixed in.

:So the best thing would be, if sunsite and the archive did agree on
:the numbering.

OK, well, if you're willing to make a small change to ezmlm-idx - which
won't affect your other lists; the change would allow sublists to have
more than one possible parent list - and you're also willing to make some
structural changes to the list setup - using five list hierarchies, not
three then, yes, a message to announce will have an announce number even
when sent to users or workers.  And a message to users will have a users
number when sent to workers.

I'll mail details later.
-- 
Geoff Wing   <gcw@pobox.com>            Mobile : (Australia) 0412 162 441
Work URL: http://www.primenet.com.au/   Ego URL: http://pobox.com/~gcw/


  reply	other threads:[~1999-01-28  3:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <990126210538.ZM26432@candle.brasslantern.com>
1999-01-27  5:19 ` Geoff Wing
1999-01-27  5:32   ` Bart Schaefer
1999-01-27  5:58     ` Geoff Wing
1999-01-27  6:55       ` Geoff Wing
1999-01-27  7:22         ` Bart Schaefer
1999-01-27  9:23           ` Geoff Wing
1999-01-27  9:44           ` Karsten Thygesen
1999-01-27 10:06             ` Geoff Wing
1999-01-27 14:39               ` Karsten Thygesen
1999-01-27 16:15                 ` Bart Schaefer
1999-01-27 17:55         ` Karsten Thygesen
1999-01-28  3:38           ` Geoff Wing [this message]
1999-01-28 16:14             ` Bart Schaefer
1999-01-28 18:13               ` Geoff Wing

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=slrn7avmsu.1br.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).