From: Jason Molenda <jason-swarelist@molenda.com>
To: overseers@sources.redhat.com
Subject: Re: [dcramer@motive.com: New messages posted after 3/21 not appearing in sources.redhat.com archives]
Date: Thu, 27 Mar 2003 23:58:00 -0000 [thread overview]
Message-ID: <20030327160236.A19216@molenda.com> (raw)
In-Reply-To: <20030327235453.GB30783@redhat.com>; from cgf@redhat.com on Thu, Mar 27, 2003 at 06:54:55PM -0500
Maybe it's just that I'm really sick today, but I don't know if I'll
bother resubscribing them (that's what it looks like happened). These
lists used to have no good web archives, but I'm sure the oasis-open.org
site is doing something reasonable.
I might have a more generous opinion on this when I'm feeling better,
but at this moment it's hard to make myself want to clean up after
whatever the mailing list administrator did on those lists.
J
On Thu, Mar 27, 2003 at 06:54:55PM -0500, Christopher Faylor wrote:
> ----- Forwarded message from David Cramer <dcramer@motive.com> -----
>
> From: "David Cramer" <dcramer@motive.com>
> To: <sourcemaster@sources.redhat.com>
> Subject: New messages posted after 3/21 not appearing in sources.redhat.com archives
> Date: Thu, 27 Mar 2003 17:06:53 -0600
>
> Hi there,
> I thought you'd like to know that http://sources.redhat.com/ml/docbook/
> and http://sources.redhat.com/ml/docbook-apps/ are missing new messages
> posted since 3/21. Compare them with the archive at oasis:
> http://lists.oasis-open.org/archives/docbook-apps/ and
> http://lists.oasis-open.org/archives/docbook/
>
> Something's been going on with those lists-several people, myself
> included, were bumped off recently and had to resubscribe.
>
> David
>
> ----- End forwarded message -----
prev parent reply other threads:[~2003-03-27 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 23:54 Christopher Faylor
2003-03-27 23:58 ` Jason Molenda [this message]
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=20030327160236.A19216@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sources.redhat.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).