public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
Subject: Fwd: public-inbox for cygwin lists
Date: Tue, 13 Sep 2022 22:02:09 +0100	[thread overview]
Message-ID: <> (raw)

-------- Forwarded Message --------
Subject: public-inbox for cygwin lists
Date: Thu, 25 Aug 2022 13:03:24 +0200
From: Mark Wielaard <>

Hi cygwin-hackers,

Given that cygwin is part of the sourceware family the mailinglists are
now also available through the public-inbox instance at

In particular:

There are also archives of some older not used anymore lists in case
people are interested in some history (we are aware that some of these
older lists contain spam, we will try to remove that).

Note that you can now mirror these mailinglists through git (see the
mirror instructions on each list), there is an atom link to follow the
lists, you can download mboxes of search results and there are read-
only nntp news and imap archives of each list (in the inbox.cygwin.*

To handle patches you might want to look at b4 or piem for emacs:

You will want the following in your .git/config:

     midmask =
     linkmask =

There are currently some known issues:

- Message-IDs can contain slashes ('/') which are sometimes
   encoded as %2F. If you got an URL with "%2F" in the path change
   it to an actual '/' character to workaround it
   (which doesn't work if the Message-ID ends with a /).
   We are looking to see if we can get the slash handling more

- HTML emails aren't accepted. Even if the list would strip the
   text/html part. Please don't sent HTML email. We are looking
   at stripping the HTML part and only importing the text/plain
   part into public-inbox.

Your friendly sourceware overseers team (with special thanks to Simon
Marchi for showing how to setup public-inbox and to Frank Eigler for
making sure the sourceware infrastructure was ready).

                 reply	other threads:[~2022-09-13 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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