From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 60D353858C52 for ; Fri, 9 Sep 2022 17:00:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 60D353858C52 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id EC89F30067AC; Fri, 9 Sep 2022 19:00:28 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id A111B2E80366; Fri, 9 Sep 2022 19:00:28 +0200 (CEST) Date: Fri, 9 Sep 2022 19:00:28 +0200 From: Mark Wielaard To: Akari Takahashi Cc: gcc@gcc.gnu.org Subject: Re: Sourceware accepted as SFC member project Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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