[PATCH] Indicate what happens to CLOCK entries in cloned subtrees

[Samuel Loury <konubinix@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 132 bytes --]

Hello,

This is a very small documentation patch to explain to the user what
will happen to the CLOCK entries of a cloned subtree.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-Indicate-what-happens-to-CLOCK-entries-in-cloned-sub.patch --]
[-- Type: text/x-diff, Size: 1108 bytes --]

From ea902d50e85c406376f5d54cf0e1652b7afaef26 Mon Sep 17 00:00:00 2001
From: Konubinix <konubinix@gmail.com>
Date: Fri, 23 Jan 2015 08:53:47 +0100
Subject: [PATCH] Indicate what happens to CLOCK entries in cloned subtrees

* lisp/org.el (org-clone-subtree-with-time-shift): Add into the documentation
  string a precision about the deletion of the CLOCK entries into the cloned
  subtrees. Indicate the rational for this decision.
---
 lisp/org.el | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/lisp/org.el b/lisp/org.el
index a8ede1d..357731a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8903,6 +8903,9 @@ stamps in the subtree shifted for each clone produced.  If SHIFT
 is nil or the empty string, time stamps will be left alone.  The
 ID property of the original subtree is removed.
 
+In each clone, all the CLOCK entries will be removed. This prevents
+org-mode for considering that the clocked times overlap.
+
 If the original subtree did contain time stamps with a repeater,
 the following will happen:
 - the repeater will be removed in each clone
-- 
2.9.3


[-- Attachment #1.3: Type: text/plain, Size: 104 bytes --]

-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]