From: Devin Ulibarri <devinu@fsf.org>
To: libreplanet-discuss@libreplanet.org
Subject: Schedule for LibrePlanet 2022
Date: Fri, 25 Feb 2022 16:28:09 -0500 [thread overview]
Message-ID: <1b12ba20-13fa-3346-d5d3-207a0193f661@fsf.org> (raw)
Hi dear fellow friends in freedom,
Hope all is well.
We are please to announce the schedule for LibrePlanet!
Please see
https://www.fsf.org/blogs/community/the-libreplanet-2022-living-liberation-schedule-is-here-for-19-20-march
for details.
For those subscribed to this list on Mastodon, please consider boosting
https://hostux.social/@fsf/107860737086197233
Yours in freedom,
Devin
--
Devin Ulibarri // Outreach & Communications Coordinator
Free Software Foundation
Join the FSF and help us defend software freedom: https://my.fsf.org/
US government employee? Use CFC charity code 63210 to support us through
the Combined Federal Campaign. https://cfcgiving.opm.gov/
GPG Key: 2E0E CE75 F816 2B40 7D66 6767 8797 38E6 D644 0D57
What's GPG? See https://emailselfdefense.fsf.org/ for more info.
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
reply other threads:[~2022-02-25 22:46 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.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b12ba20-13fa-3346-d5d3-207a0193f661@fsf.org \
--to=devinu@fsf.org \
--cc=libreplanet-discuss@libreplanet.org \
/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).