From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id DB193383D00C for ; Fri, 18 Jun 2021 20:37:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DB193383D00C Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-433-q56p6QZ-M5ehE0lujxxilA-1; Fri, 18 Jun 2021 16:37:36 -0400 X-MC-Unique: q56p6QZ-M5ehE0lujxxilA-1 Received: by mail-qk1-f197.google.com with SMTP id i3-20020a05620a1503b02903b24f00c97fso1107142qkk.21 for ; Fri, 18 Jun 2021 13:37:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=YTTDgQFl+Xxko/2pFyVqGdrCuJYm1haISyaRGX1WJt8=; b=Qavnsx9/jsciClYlwP0jJdaHapolwwOSzYdsa51d7cmCTjE/KufHztckQUNi2BrRqW St050Cp7WS3mJGH6GQ8g5kFboJpeMsIcMxejnQRflNoLGa8bSuTTM54Zs5Txecx8MGMY gtawQq+J3ZDu+EnECEqT2payi+EQtMorCvYmJIC9M8bd3TBJDtcCRZqzKW6SEv7yf4c0 NH18OkIP582OxFOLotlM+4iHQvDUcT8PzEgTej/OYGSETYmLo4/zI3utjifEyu5AfjkG CrqNsj+3wj32jEQ+RwenWr3pIxcsdgXuGS7klsJaeSlLzmkgdFIsbGgqLc1hUTKv5rTr EKbA== X-Gm-Message-State: AOAM532rxHOb+UAeeNStAO4br3wTKz2NenhPP+GstF+5MarCoQft0WoE myi8Fg0rzYuhspYJeLyGzugI/xqTrpn2BXorDMlRUmwncf1DB7AdS/U0z56b8wArdkT+1yN7jD0 ObnsVTX0= X-Received: by 2002:ac8:7dc6:: with SMTP id c6mr5756891qte.127.1624048655635; Fri, 18 Jun 2021 13:37:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxJpjK3VKih09b7x+6eXrBxB5zC5+Z9DPAHGaXOng4H93LgN5gKuGTRobV2qQ2jCCsCv/yukQ== X-Received: by 2002:ac8:7dc6:: with SMTP id c6mr5756872qte.127.1624048655369; Fri, 18 Jun 2021 13:37:35 -0700 (PDT) Received: from t14s.localdomain (c-73-69-212-193.hsd1.nh.comcast.net. [73.69.212.193]) by smtp.gmail.com with ESMTPSA id y3sm4711144qkf.2.2021.06.18.13.37.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Jun 2021 13:37:34 -0700 (PDT) Message-ID: Subject: Re: [PATCH] libgccjit: add some reflection functions in the jit C api From: David Malcolm To: Antoni Boucher Cc: Antoni Boucher via Jit , gcc-patches@gcc.gnu.org Date: Fri, 18 Jun 2021 16:37:33 -0400 In-Reply-To: <711092bc80237e32caa48f2060c93be30cb9c220.camel@zoho.com> References: <20200902010120.crnx55ev635ceiey@bouanto-desktop.localdomain> <6fe2ea355403eb177c9632e076c11c792f23c791.camel@redhat.com> <9cd00fe5cb5c03184e3a5bd939447b30450a8ca7.camel@redhat.com> <20201015160226.cka4iq3w22jztopm@bouanto-desktop.localdomain> <20201015173952.ft7mu5ajbaxb3gke@bouanto-desktop.localdomain> <54ba5c58dbd2b8c7b1f3276c2b87cddf55e258bd.camel@redhat.com> <20201103221324.xw3jbvrw2uwdc4rz@bouanto-desktop.localdomain> <3388bb8c84e68cd7b0698dc154e7a5666c0d2cde.camel@redhat.com> <0e8b6450bcb23182b85342d8010c3bea0c297ba2.camel@zoho.com> <534254132a841b75d555a52ce952f84418f168c2.camel@redhat.com> <3c328b40570b10b22a8925fd64b2781dc9264358.camel@zoho.com> <715f6ebfe1627fc39d8ec3b15f1e38f8378f3db7.camel@redhat.com> <711092bc80237e32caa48f2060c93be30cb9c220.camel@zoho.com> User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: jit@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Jit mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2021 20:37:48 -0000 On Fri, 2021-06-18 at 15:41 -0400, Antoni Boucher wrote: > I have write access now. Great. > I'm not sure how I'm supposed to send my patches: > should I put it in personal branches and you'll merge them? Please send them to this mailing list for review; once they're approved you can merge them. > > And for the MAINTAINERS file, should I just push to master right > away, > after sending it to the mailing list? I think people just push the MAINTAINERS change and then let the list know, since it makes a good test that write access is working correctly. Dave > > Thanks for your help! > > Le vendredi 18 juin 2021 à 12:09 -0400, David Malcolm a écrit : > > On Fri, 2021-06-18 at 11:55 -0400, Antoni Boucher wrote: > > > Le vendredi 11 juin 2021 à 14:00 -0400, David Malcolm a écrit : > > > > On Fri, 2021-06-11 at 08:15 -0400, Antoni Boucher wrote: > > > > > Thank you for your answer. > > > > > I attached the updated patch. > > > > > > > > BTW you (or possibly me) dropped the mailing lists; was that > > > > deliberate? > > > > > > Oh, my bad. > > > > > > > [...] > > > > > > > > > > > > > > > > > I have signed the FSF copyright attribution. > > > > > > > > I can push changes on your behalf, but I'd prefer it if you did > > > > it, > > > > especially given that you have various other patches you want > > > > to > > > > get > > > > in. > > > > > > > > Instructions on how to get push rights to the git repo are > > > > here: > > > >   https://gcc.gnu.org/gitwrite.html > > > > > > > > I can sponsor you. > > > > > > Thanks. > > > I did sign up to get push rights. > > > Have you accepted my request to get those? > > > > I did, but I didn't see any kind of notification.  Did you get an > > email > > about it? > > > > > > Dave > > > >