From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-109743-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 10510 invoked by alias); 24 Jan 2014 16:05:06 -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 10501 invoked by uid 89); 24 Jan 2014 16:05:06 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-oa0-f53.google.com
Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 24 Jan 2014 16:05:05 +0000
Received: by mail-oa0-f53.google.com with SMTP id m1so4011943oag.12        for <gdb-patches@sourceware.org>; Fri, 24 Jan 2014 08:05:03 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.196.3 with SMTP id ii3mr12644134obc.11.1390579503538; Fri, 24 Jan 2014 08:05:03 -0800 (PST)
Received: by 10.76.105.174 with HTTP; Fri, 24 Jan 2014 08:05:03 -0800 (PST)
In-Reply-To: <83mwilcqqk.fsf@gnu.org>
References: <20140124080703.GL4762@adacore.com>	<83eh3xep43.fsf@gnu.org>	<CANu=DmhEyNvF3au1r+zyrZ2B368iA8PF3hh3cWMM2Hhwa1mpYw@mail.gmail.com>	<83a9eleksf.fsf@gnu.org>	<CANu=Dmh39cA462XRa=+254n3CwZ5M3peAQBhN-bhV6A6OuXuzQ@mail.gmail.com>	<838uu5eju2.fsf@gnu.org>	<20140124105807.GM4762@adacore.com>	<837g9peirg.fsf@gnu.org>	<20140124113014.GN4762@adacore.com>	<8361p9ehht.fsf@gnu.org>	<20140124115548.GO4762@adacore.com>	<83wqhpcv4z.fsf@gnu.org>	<CAMe9rOpU3QeMuNveNMYVXJh0xn+WG5eH-LLw7Gw7OLf8qj--Eg@mail.gmail.com>	<83ob31crka.fsf@gnu.org>	<CAMe9rOqUAYb_CzhAwTfoGGP29GabufJjsP60sS-csZY_-Nnbzg@mail.gmail.com>	<83mwilcqqk.fsf@gnu.org>
Date: Fri, 24 Jan 2014 16:05:00 -0000
Message-ID: <CAMe9rOpCVo0k5q58vgSW2MOiTiZBmUKXJLcqER8YhQVpQEiTDQ@mail.gmail.com>
Subject: Re: reject merges on gdb release branches?
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>, Will Newton <will.newton@linaro.org>, 	ricard.wanderlof@axis.com, GDB <gdb-patches@sourceware.org>
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
X-SW-Source: 2014-01/txt/msg00945.txt.bz2

On Fri, Jan 24, 2014 at 8:02 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 24 Jan 2014 07:49:08 -0800
>> From: "H.J. Lu" <hjl.tools@gmail.com>
>> Cc: Joel Brobecker <brobecker@adacore.com>, Will Newton <will.newton@linaro.org>,
>>       ricard.wanderlof@axis.com, GDB <gdb-patches@sourceware.org>
>>
>> How can you do "git bisect" with merged commits?  I
>
> Like this:
>
>   https://gist.github.com/canton7/3737126
>
> And in any case, if somehow this is not your case, you can always
> start a new bisect with the commits on the branch as start and end
> points.

I may live with this complicated workaround on my personal branches.
But I won't force it upon other developers.

-- 
H.J.