From: Akari Takahashi <akaritakahashioss@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Sourceware accepted as SFC member project
Date: Sat, 10 Sep 2022 00:53:26 +0900 [thread overview]
Message-ID: <CAPzzfcvcnsKdLwjifC0ULNQEnERH+Oe2nYnae49_7nLGbkWtyA@mail.gmail.com> (raw)
In-Reply-To: <YxpzFkSrrPNnjOIC@wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Hello there,
I am very pleased to hear from you.
I read the linked message exchange carefully. After that, I tried to git
clone the Git repository following the steps in the link below, but I get a
permission error message. What are the next steps?
https://gcc.gnu.org/gitwrite.html#setup
I posted to the following mailing list before this application.
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601320.html
Best Regards,
Takahashi Akari
GPG Key: 9DD8 F529 83A0 3182 D318 6184 9309 E8D2 2FD4 4365
On Fri, Sep 9, 2022 at 7:56 AM Mark Wielaard <mark@klomp.org> wrote:
>
> Hi,
>
> We are very grateful for the public replies and suggestions received
> to our proposal, which were all very positive. And we are happy to
> report that the SFC's Evaluations Committee has voted to accept
> Sourceware as a Conservancy member project. If people are interested
> in, or want to help out with, the next steps they are invited to join
> the sourceware overseers list.
>
> https://sourceware.org/pipermail/overseers/2022q3/018834.html
>
> Thanks,
>
> Chris Faylor <cgf@sourceware.org>
> Frank Eigler <fche@sourceware.org>
> Mark Wielaard <mark@klomp.org>
next prev parent reply other threads:[~2022-09-09 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 18:48 Proposing Sourceware " Mark Wielaard
2022-09-08 22:56 ` Sourceware accepted " Mark Wielaard
2022-09-09 15:53 ` Akari Takahashi [this message]
2022-09-09 17:00 ` Mark Wielaard
2022-09-10 16:24 ` Akari Takahashi
2022-11-15 21:45 ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
2022-12-31 22:57 ` Mark Wielaard
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=CAPzzfcvcnsKdLwjifC0ULNQEnERH+Oe2nYnae49_7nLGbkWtyA@mail.gmail.com \
--to=akaritakahashioss@gmail.com \
--cc=gcc@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).