zsh-workers
 help / color / mirror / code / Atom feed
From: Karsten Thygesen <karthy@kom.auc.dk>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: List archive not tracking new home site?
Date: 27 Jan 1999 10:44:00 +0100	[thread overview]
Message-ID: <yd8zp75gie7.fsf@yugo.kom.auc.dk> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Tue, 26 Jan 1999 23:22:00 -0800"

>>>>> "Bart" == Bart Schaefer <schaefer@brasslantern.com> writes:

Bart> On Jan 27, 6:55am, Geoff Wing wrote: } Subject: Re: List archive
Bart> not tracking new home site?  } } Comments?

Bart> Since I presume you're looking at ezmlm documentation or some
Bart> such ...

Bart> The problem appears to be that when list A forwards to list B,
Bart> the X-Seq: header from A is replaced by the one from B.  Yes?
Bart> So people only on zsh-users see a different X-Seq: from those on
Bart> zsh-workers?

Bart> Would it be possible to simply configure qmail/ezmlm to move the
Bart> old X-Seq: header to some other name (possibly derived from the
Bart> existing Mailing-List: header) before adding the new X-Seq: and
Bart> Mailing-List: ?

Bart> I don't particularly care whether zsh-users messages are
Bart> duplicated in the zsh-workers archive (whether the HTTP one or
Bart> the listserver one); in fact that'd make it easier to find
Bart> things.  I *do* object to losing the -users sequence number
Bart> entirely when the message is forwarded.

How about having a X-Seq-users AND a X-Seq-workers and X-Seq-announce?
That way, forwarded messages will contain all (possible) sequence
numbers, and intelligent archive software could even use this to
crosslink between the lists. 

Comments?

Karsten


  parent reply	other threads:[~1999-01-27  9:44 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 [this message]
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
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=yd8zp75gie7.fsf@yugo.kom.auc.dk \
    --to=karthy@kom.auc.dk \
    --cc=schaefer@brasslantern.com \
    --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).