public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Two naive questions
Date: Tue, 21 Apr 2020 12:33:59 -0600	[thread overview]
Message-ID: <f81519ec-8325-03c4-9037-96d83edc02c5@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200420201404.GB10790@cgf.cx>

On 2020-04-20 14:14, Christopher Faylor wrote:
> On Mon, Apr 20, 2020 at 11:59:08AM -0600, Brian Inglis wrote:
>> The new server ml archive does not seem to offer the metadata available on the
>> previous server and archive, and that is true of most archives that do not allow
>> replies: probably a good way to reduce space required by 50-90%, from what I can
>> see.
>> A subscribed user could provide you with the reply References header values.
> This is a text cut and paste from https://cygwin.com/pipermail/cygwin/
>     The Cygwin Archives
>     You can get more information about this list.
>     Archive 	View by: 	Downloadable version
>     April 2020: 	[ Thread ] [ Subject ] [ Author ] [ Date ] 	[ Gzip'd Text 110 KB ]
> Notice the "Gzip'd Text ..."?
> That's the mbox formatted email archives.

I imported them all into Thunderbird to be able to search locally, as all
archive search tools seem to be worse than any of the search sites in
determining relevance or providing *all* relevant results newest first, while
the builtin tools allow searching on header field combos, and there is always
grep/sed/awk thru the mozmsgs maildirs for the really fuzzy searches.

Your previous reply was probably the best that can be done with pipermail
archives on mailman 2.1, although I am surprised you did not go to mailman 3
with hyperkitty on the new servers.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  reply	other threads:[~2020-04-21 18:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 20:21 Fergus Daly
2020-04-17  5:10 ` Marco Atzeri
2020-04-17 11:17   ` Fergus Daly
2020-04-17 17:31     ` Brian Inglis
2020-04-17 17:49   ` Stephen Carrier
2020-04-17 18:16     ` Andrey Repin
2020-04-17 18:44       ` Brian Inglis
2020-04-20 17:20         ` Stephen Carrier
2020-04-20 17:41           ` Bill Stewart
2020-04-20 18:11             ` Eliot Moss
2020-04-20 18:51               ` Bill Stewart
2020-04-20 20:09             ` Christopher Faylor
2020-04-20 20:44               ` Bill Stewart
2020-04-20 23:51                 ` Christopher Faylor
2020-04-21 16:47               ` Stephen Carrier
2020-04-22  9:57             ` Andrey Repin
2020-04-23 16:49               ` Stephen Carrier
2020-04-23 19:13                 ` Christopher Faylor
2020-04-23 19:33                   ` Christopher Faylor
2020-04-24 18:58                   ` Stephen Carrier
2020-04-25 15:18                     ` Christopher Faylor
2020-04-20 17:59           ` Brian Inglis
2020-04-20 20:14             ` Christopher Faylor
2020-04-21 18:33               ` Brian Inglis [this message]
2020-04-21 20:30                 ` Mailing list musings (was Re: Two naive questions) Christopher Faylor
2020-04-19  2:58 ` Two naive questions Christopher Faylor

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=f81519ec-8325-03c4-9037-96d83edc02c5@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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).