From: "Michael Kjörling" <email@example.com>
Subject: [TUHS] Re: X11 Conservancy Project
Date: Sun, 25 Dec 2022 19:57:36 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 25 Dec 2022 19:16 +0000, from email@example.com (segaloco via TUHS):
> Does the project accept patches to old X11 applications to get them
> working again?
The "X11CP repository" link on the web site goes to
https://codeberg.org/x11cp/x11cp which has a README that, under
"Contributing", among other things lists "Source-code modification".
There is also a recent patch committed that explicitly says "add
compilation fixes" and "This makes gcc happier". See
By deduction, I would expect patches that allows old software to
compile and execute on modern systems, while remainining true to the
experience of running those applications in their original
environment, to qualify for inclusion.
There is also multiple points of contact listed, by way of which you
could almost certainly get an authoritative answer.
Michael Kjörling 🏡 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
next prev parent reply other threads:[~2022-12-25 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 18:15 [TUHS] " Michelangelo De Simone
2022-12-25 19:16 ` [TUHS] " segaloco via TUHS
2022-12-25 19:57 ` Michael Kjörling [this message]
2022-12-25 20:51 ` [TUHS] OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project) G. Branden Robinson
2022-12-25 21:03 ` [TUHS] " Brad Spencer
2022-12-25 21:38 ` josh
2022-12-25 21:47 ` Ron Natalie
2022-12-26 6:26 ` arnold
2022-12-26 19:37 ` Jon Steinhart
2022-12-26 4:18 ` Warner Losh
2022-12-26 9:59 ` [TUHS] Re: X11 Conservancy Project Lars Brinkhoff
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 NNTP newsgroup(s).