From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Karsten Thygesen <karthy@kom.auc.dk>, mason@primenet.com.au
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: List archive not tracking new home site?
Date: Wed, 27 Jan 1999 08:15:40 -0800 [thread overview]
Message-ID: <990127081541.ZM28632@candle.brasslantern.com> (raw)
In-Reply-To: <yd8ww28g4pj.fsf@yugo.kom.auc.dk>
On Jan 27, 3:39pm, Karsten Thygesen wrote:
} Subject: Re: List archive not tracking new home site?
}
} No - now that I give it a second thought, you are right.
This is not giving me great vibes about ezmlm.
} Anyway - what other solutions can we come up with? Is there anybody or
} anything besides the mail archive that uses the sequence numbers to
} anything?
Yes. When a patch gets applied, the ChangeLog file (or my own CVS commit
logs, or PWS's patchlist.txt file) get the article number (formerly from
the X-Mailing-List header) inserted into the log. That way anybody who
wants to can go back to the original article to find out exactly what
changed and what discussion led to the change.
It's very important IMO that the article number on the HTTP archive site
be the same as the one that appears on the message headers.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-01-27 16:15 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 [this message]
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=990127081541.ZM28632@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=karthy@kom.auc.dk \
--cc=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).