From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-124973-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 54330 invoked by alias); 4 Aug 2015 16:14:56 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 54319 invoked by uid 89); 4 Aug 2015 16:14:55 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2
X-HELO: mx1.redhat.com
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 04 Aug 2015 16:14:50 +0000
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])	by mx1.redhat.com (Postfix) with ESMTPS id CC04596D3;	Tue,  4 Aug 2015 16:14:48 +0000 (UTC)
Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11])	by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t74GEkPo010623;	Tue, 4 Aug 2015 12:14:47 -0400
Message-ID: <55C0E4F6.5080703@redhat.com>
Date: Tue, 04 Aug 2015 16:14:00 -0000
From: Pedro Alves <palves@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Iain Buclaw <ibuclaw@gdcproject.org>
CC: Joel Brobecker <brobecker@adacore.com>,        GDB Patches <gdb-patches@sourceware.org>,        Luis Machado <lgustavo@codesourcery.com>
Subject: Re: [PATCH] bfd: Fix regression when building bfd on mingw32
References: <CABOHX+fAiKiNgmns+FRY_tuNbEhvvvdQWD=LD4ENcX-O2yeaFQ@mail.gmail.com>	<20150804154157.GA4777@adacore.com>	<CABOHX+d8D-GCz36m1fwvMV2EphRe01eEVrbYWZx9+PEVxEtL-w@mail.gmail.com>	<55C0E066.9040805@redhat.com> <CABOHX+dKK8ke0JZDjdcaHYdsYv==ksHGx7Z+YpiW=ijqRvc=Bw@mail.gmail.com>
In-Reply-To: <CABOHX+dKK8ke0JZDjdcaHYdsYv==ksHGx7Z+YpiW=ijqRvc=Bw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2015-08/txt/msg00088.txt.bz2

On 08/04/2015 05:09 PM, Iain Buclaw wrote:

> Will have to wait until this evening if that's OK.  

That's super fine.

> Is there a general
> guideline on pushing patches to branch?  I assume that you don't do
> anything fancy with git such as merge or cherry-pick.

Nothing fancy.  non-fast-forward merges are disabled, the server
rejects them.  So to push to branch, simply rebase the patch on top of
the branch and then push to it.  cherry-picking is fine as it's just a
way to get the patch in the first place.

Thanks,
Pedro Alves