From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18964 invoked by alias); 22 Nov 2013 07:43:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 18947 invoked by uid 89); 22 Nov 2013 07:43:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_05,RDNS_NONE autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: rock.gnat.com Received: from Unknown (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 22 Nov 2013 07:43:54 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 93D5F11686C; Fri, 22 Nov 2013 02:44:20 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dtG9NePO5u7I; Fri, 22 Nov 2013 02:44:20 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 18FBB11686A; Fri, 22 Nov 2013 02:44:20 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 8A51DE993A; Fri, 22 Nov 2013 11:43:41 +0400 (RET) Date: Fri, 22 Nov 2013 08:17:00 -0000 From: Joel Brobecker To: "Maciej W. Rozycki" , Tom Tromey Cc: Tristan Gingold , Richard Sandiford , binutils@sourceware.org, gdb-patches@sourceware.org Subject: Re: Release 2.24 Message-ID: <20131122074341.GA3321@adacore.com> References: <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com> <20130918213245.GO3132@adacore.com> <20131118172117.GD3481@adacore.com> <20131122021904.GN3481@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131122021904.GN3481@adacore.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-11/txt/msg00673.txt.bz2 > . Once that's done, I have 2 options: > > (1) Create the new relase off the git repository, but create > the release either manually or with the new scripts; > > (2) Push the commit to the CVS repo, and re-use the old > scripts to make the release. > > If it's only a handful of patches, my preference would be to play it > safe, and go with option (2). Pushing the patches to the CVS repo is > super easy thanks to "git cvsexportcommit", but we will need the help > of someone like Tom to temporary re-open the CVS (or, if Tom prefers, > he can cvsexportcommit the patches himself, and let us know when he > is done). On second thoughts, there is fairly significant drawback in using the CVS repository. The release process involves making some commits as well as creating a tag, and we would want all of that in our git repo. If we use the CVS repository, we'll have to import those changes back from CVS into git. I'm starting to lean towards doing everything in git, and fixup any problem if necessary. -- Joel