From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: Re: Toolchain Infrastructure project statement of support
Date: Mon, 24 Oct 2022 14:40:50 +0200 [thread overview]
Message-ID: <Y1aH0nx5UNnf1hJ1@calimero.vinschen.de> (raw)
In-Reply-To: <0bac951e-8f5e-deb6-c126-26d5fbd0bbfe@gotplt.org>
On Oct 23 12:07, Siddhesh Poyarekar via Overseers wrote:
> I am not aware of any opposition from maintainers of libabigail or cygwin or
> any other active sourceware based project over moving either, but I haven't
> had any links to those projects, so I may be uninformed.
For the time being, as the project lead, I hearby declare that Cygwin
and the cygwin.com domain wants to stay on Sourceware. We have exactly
what we need on sware, so I don't see any reason to move infrastructure
to another entity, which we, in fact, don't really know much about, and
which may just add additional red tape.
"For the time being", because I didn't take the prospect of moving sware
in its entirety to some 3-rd part service really serious. I still have
to discuss this with other Cygwin maintainers, but I have a hard time
to see that there's any real advantage for Cygwin.
Corinna
next prev parent reply other threads:[~2022-10-24 12:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 16:43 Carlos O'Donell
2022-10-12 18:13 ` Andrew Pinski
2022-10-13 18:25 ` Christopher Faylor
2022-10-14 12:33 ` Siddhesh Poyarekar
2022-10-17 15:10 ` Mark Wielaard
2022-10-17 16:11 ` Siddhesh Poyarekar
2022-10-18 9:50 ` Mark Wielaard
2022-10-18 15:17 ` Siddhesh Poyarekar
2022-10-18 16:42 ` Christopher Faylor
2022-10-18 18:13 ` Siddhesh Poyarekar
2022-10-18 18:14 ` Siddhesh Poyarekar
2022-10-18 18:47 ` Paul Smith
2022-10-21 0:33 ` Alexandre Oliva
2022-10-23 8:59 ` Ian Kelling
2022-10-23 13:27 ` Siddhesh Poyarekar
2022-10-23 15:16 ` Frank Ch. Eigler
2022-10-23 16:07 ` Siddhesh Poyarekar
2022-10-23 16:32 ` Siddhesh Poyarekar
2022-10-23 17:01 ` Jeff Law
2022-10-23 22:35 ` Christopher Faylor
2022-10-23 17:09 ` Frank Ch. Eigler
2022-10-23 17:38 ` Jeff Law
2022-10-24 1:51 ` Siddhesh Poyarekar
2022-10-24 12:40 ` Corinna Vinschen [this message]
2022-10-23 20:57 ` Christopher Faylor
2022-10-23 21:17 ` Siddhesh Poyarekar
2022-10-23 21:59 ` Christopher Faylor
2022-10-24 1:29 ` Siddhesh Poyarekar
2022-10-23 11:33 ` Ian Kelling
2022-10-23 16:17 ` Siddhesh Poyarekar
2022-10-23 18:56 ` Konstantin Ryabitsev
2022-10-23 21:19 ` Alexandre Oliva
2022-10-23 22:07 ` Christopher Faylor
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=Y1aH0nx5UNnf1hJ1@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=overseers@sourceware.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).