public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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: Sun, 11 Sep 2022 01:24:12 +0900	[thread overview]
Message-ID: <CAPzzfcu4Ck-C-DpdqOruokSMQQ+yMkuu31d6N4sj4pjJ_OezsQ@mail.gmail.com> (raw)
In-Reply-To: <YxtxLETPTNSgnxoa@wildebeest.org>

Hi,

Thanks to the goodwill of the GCC maintainer, my name was included in
the commit log.
I would like to take this opportunity to study more and contribute to
free and very important software such as GCC.
https://github.com/gcc-mirror/gcc/commit/16d752a514033a9e37fed2a7f78024e222ca26b9

Best Regards,
Takahashi Akari
GPG Key: 9DD8 F529 83A0 3182 D318 6184 9309 E8D2 2FD4 4365

On Sat, Sep 10, 2022 at 2:00 AM Mark Wielaard <mark@klomp.org> wrote:
>
> Hi,
>
> On Sat, Sep 10, 2022 at 12:53:26AM +0900, Akari Takahashi via Gcc wrote:
> > 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
>
> Your patch is unnecessary, the brackets are added by the
> MEM_SIZE_KNOWN_P define.  You don't need git write access. If you post
> a proper patch someone will review it and commit it for you. This is
> an offtopic request in this email thread. Please stop trying to get
> git write access by writing to various mailing lists, if you need it
> someone will tell you and point you to the proper process to follow.
>
> Thanks,
>
> Mark

  reply	other threads:[~2022-09-10 16:24 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
2022-09-09 17:00     ` Mark Wielaard
2022-09-10 16:24       ` Akari Takahashi [this message]
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=CAPzzfcu4Ck-C-DpdqOruokSMQQ+yMkuu31d6N4sj4pjJ_OezsQ@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).