From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jorge Morais Neto <jorge13515@gmail.com>
Subject: Re: Release 9.0.5
Date: Fri, 10 Feb 2017 17:50:32 -0200
Message-ID: <CAJR3QnedcimBfN_A4qcVu0TS0A=onPFzAMAVc8v6eGOj4T5KBQ@mail.gmail.com>
References: <8737fmxibv.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47230)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jorgepeixotomorais@gmail.com>) id 1ccHDL-0006bV-0S
	for emacs-orgmode@gnu.org; Fri, 10 Feb 2017 14:50:40 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jorgepeixotomorais@gmail.com>) id 1ccHDJ-0006Wl-Ng
	for emacs-orgmode@gnu.org; Fri, 10 Feb 2017 14:50:38 -0500
In-Reply-To: <8737fmxibv.fsf@gnu.org>
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: Bastien <bzg@gnu.org>
Cc: org mode <emacs-orgmode@gnu.org>

On 10 February 2017 at 11:53, Bastien <bzg@gnu.org> wrote:
> Org 9.0.5, a minor bugfix release, is out.
In Org 9.0.5, clock out notes are again stored below the corresponding
clock line, restoring the behavior of an earlier release.  There were
interim releases, up to 9.0.4, that stored the clock out notes /above/
the clock line. Users should be warned to fix clock out notes taken by
affected Org releases.  Existing important data following the interim
convention need to be fixed, transposing each affected clock out note
with the clock line.  If both conventions are mixed, then, to identify
which clock line corresponds to each clock out note, either the user
will need to remember the time period when they used an affected
release, or remember directly which clock out line corresponds to each
ambiguous note, or analise the version history of their Org files.  So
the longer the user takes to address the problem, the greater the
chance of data loss.  I think this issue is important.

Could we provide an Elisp function to fix this semi-automatically?

Regards
--=20
=E2=80=A2 I am Brazilian.  I hope my English is correct and I welcome corre=
ctions.
=E2=80=A2 Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM a=
nd 7z.
=E2=80=A2 Free (as in free speech) software for Android: https://f-droid.or=
g/