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 [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 0DEFB38515D6 for ; Thu, 19 May 2022 08:27:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0DEFB38515D6 Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-42-WNrab7nfPoSiJqWI5KWDig-1; Thu, 19 May 2022 04:27:42 -0400 X-MC-Unique: WNrab7nfPoSiJqWI5KWDig-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5E59329AA2ED; Thu, 19 May 2022 08:27:42 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.192.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1F62B2166B25; Thu, 19 May 2022 08:27:41 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.16.1/8.16.1) with ESMTPS id 24J8RdYP071617 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 19 May 2022 10:27:39 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.16.1/8.16.1/Submit) id 24J8RcOS071616; Thu, 19 May 2022 10:27:38 +0200 Date: Thu, 19 May 2022 10:27:38 +0200 From: Jakub Jelinek To: Tobias Burnus Cc: Mohamed Atef , gcc@gcc.gnu.org Subject: Re: OMPD Branch Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2022 08:27:45 -0000 On Thu, May 19, 2022 at 09:47:34AM +0200, Tobias Burnus wrote: > Hi Mohamed, > > On 19.05.22 03:39, Mohamed Atef via Gcc wrote: > > Should I commit to devel/omp/gcc-11 branch? > > Short answer – no. Yeah, you should create a new devel/omp/ompd branch. We want a public branch in the devel/omp namespace, because the OMPD work is larger and might need several people to participate before it is finished and committing it to trunk right away might be premature until we have at least larger usable part in. Steps should be: create git clone of the gcc repository with your new gcc.gnu.org account git+ssh://mohamedatef1968@gcc.gnu.org/git/gcc.git (or tweak your existing repository such that it has origin url = git+ssh://mohamedatef1968@gcc.gnu.org/git/gcc.git ). Make sure you have run at least contrib/gcc-git-customization.sh git checkout master git checkout -b devel/omp/ompd # commit your patch, make sure the ChangeLog entry etc. are in commit log # and Signed-off-by too (as the last line) of commit message. git gcc-verify HEAD # The above should tell you if you have done something wrong with the # commit message, if so, git commit --amend it and repeat. git push -n origin devel/omp/ompd:refs/heads/devel/omp/ompd # The above as a dry run to see what it would do, if it is ok, then git push origin devel/omp/ompd:refs/heads/devel/omp/ompd Jakub