From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kyle Meyer <kyle@kyleam.com>
Subject: Re: Can't remove deadline or schedule in bulk mode
Date: Mon, 14 Aug 2017 16:33:56 -0400
Message-ID: <87378tanyj.fsf@kyleam.com>
References: <87zib7mwf6.fsf@free.fr> <87o9rnx7ho.fsf@alphapapa.net>
	<874ltep9sz.fsf@free.fr> <87lgmqp3r8.fsf@kyleam.com>
	<87zib2xn4v.fsf@free.fr> <87h8xaxffx.fsf@free.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38957)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kyle@kyleam.com>) id 1dhM3q-0007rI-8c
	for emacs-orgmode@gnu.org; Mon, 14 Aug 2017 16:34:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kyle@kyleam.com>) id 1dhM3l-0000Qk-G3
	for emacs-orgmode@gnu.org; Mon, 14 Aug 2017 16:34:06 -0400
Received: from pb-smtp1.pobox.com ([64.147.108.70]:50720
	helo=sasl.smtp.pobox.com)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <kyle@kyleam.com>) id 1dhM3l-0000Py-Bq
	for emacs-orgmode@gnu.org; Mon, 14 Aug 2017 16:34:01 -0400
In-Reply-To: <87h8xaxffx.fsf@free.fr>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Julien Cubizolles <j.cubizolles@free.fr>, emacs-orgmode@gnu.org
Cc: mail@nicolasgoaziou.fr

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> Kyle Meyer <kyle@kyleam.com> writes:
>>
>>
>>> Since you have the git repo set up and have a good/bad range, you can use
>>> git bisect to find the offending commit.
>
> I finally found the offending commit,
>
> it's commit 4f578a3f7fe193229adc239c93d6983bcc030d41 org-agenda: Small
> refactoring by N. Goaziou.

Yep, that's the same commit that I pointed to in the later part of the
message you quote, but my guess about what the problematic bits were was
wrong.  Anyway, should be fixed with b900a85fe.

-- 
Kyle