From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12344 invoked by alias); 22 Jan 2014 05:48:48 -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 12330 invoked by uid 89); 22 Jan 2014 05:48:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_00,GARBLED_BODY autolearn=no version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 22 Jan 2014 05:48:46 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1W5qg6-0005Mo-TV from Yao_Qi@mentor.com ; Tue, 21 Jan 2014 21:48:42 -0800 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 21 Jan 2014 21:48:42 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.2.247.3; Tue, 21 Jan 2014 21:47:25 -0800 Message-ID: <52DF5B39.1020209@codesourcery.com> Date: Wed, 22 Jan 2014 05:48:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Joel Brobecker CC: Subject: Re: reject merges on gdb release branches? References: <20140122051133.GB4762@adacore.com> In-Reply-To: <20140122051133.GB4762@adacore.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00845.txt.bz2 On 01/22/2014 01:11 PM, Joel Brobecker wrote: > I propose we do the same for the gdb-7.7 branch, and generally > speaking on all GDB release branches, just to make sure that > people don't accidently push a merge when they meant to cherry-pick. > Thoughts? Joel, My git knowledge is too poor to understand this. How does people push a merge? My workflow is to cherry-pick approved patches from one branch to master, and git push. I thought that is the only way to push commits to master. Am I missing something? -- Yao (齐尧)