From: Jeroen van Veen <jvanveen@protonmail.com>
To: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Pyrite moving to Codeberg
Date: Wed, 24 Jan 2024 19:25:20 +0000 [thread overview]
Message-ID: <dqtlG-ntkv97bGGT4EznYuKEbhf-t2nmzfNrK2dwXE2w6g6eMrassIiEcakMf1JFkOr7gpUG_GShoZumaHkhEUmAATJywJ1XSamMTTQ_A6g=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hi,
It's been a while since I managed to do some work on Pyrite. Hopefully, I'll be able to do some regular work on it this year. I love Galene and
like to explore some new techniques (buildtooling & automated i18n especially) for the Pyrite frontend.The project is currently hosted at Github,
but I feel uncomfortable using Microsoft's services for any longer due to their unethical practices. So, I just moved the project to https://codeberg.org/garage44/pyrite,
which is a hosted service of Forgejo. Any new work will be done on the new repo, and the old ones will be removed asap.
kind regards,
Jeroen
[-- Attachment #2: Type: text/html, Size: 2024 bytes --]
reply other threads:[~2024-01-24 19:25 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dqtlG-ntkv97bGGT4EznYuKEbhf-t2nmzfNrK2dwXE2w6g6eMrassIiEcakMf1JFkOr7gpUG_GShoZumaHkhEUmAATJywJ1XSamMTTQ_A6g=@protonmail.com' \
--to=jvanveen@protonmail.com \
--cc=galene@lists.galene.org \
--subject='Re: [Galene] Pyrite moving to Codeberg' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox