From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb@sourceware.org
Subject: Re: Sourceware joins Software Freedom Conservancy
Date: Mon, 15 May 2023 21:44:20 +0300 [thread overview]
Message-ID: <83353x1lkr.fsf@gnu.org> (raw)
In-Reply-To: <20230515181812.GO11203@gnu.wildebeest.org> (message from Mark Wielaard on Mon, 15 May 2023 20:18:12 +0200)
> Date: Mon, 15 May 2023 20:18:12 +0200
> From: Mark Wielaard <mark@klomp.org>
>
> https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/
>
> After various discussions and lots of positive feedback [1] [2] [3] [4]
> Software Freedom Conservancy and Sourceware proudly announce that
> Sourceware today joins SFC as a member project!
Any chance you (or someone else "in the know") could explain what does
this mean in practical terms? E.g., do any of the addresses and URLs
we've been using for working on GDB will change in any way? What
about access to the GDB Git repository? What about development
procedures and practices? Etc. etc.
It is a bit strange that such an announcement talks at length about
everything except what the GDB developers and contributors need to
know.
TIA
next prev parent reply other threads:[~2023-05-15 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:18 Mark Wielaard
2023-05-15 18:44 ` Eli Zaretskii via Gdb [this message]
2023-05-15 19:00 ` Mark Wielaard
2023-05-16 16:12 ` Eli Zaretskii via Gdb
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=83353x1lkr.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=eliz@gnu.org \
--cc=mark@klomp.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