From 29006606085b164fc71cb70c0337b63115b63ad5 Mon Sep 17 00:00:00 2001
From: Marc Khouzam <marc.khouzam@ericsson.com>
Date: Thu, 19 Mar 2009 18:40:57 +0000
Subject: [PATCH] [269387] Fix javadoc.  There are cases where monitor.done()
 must still be called, for instance, when calling a service on the executor
 and setting the data when the executor runs.

---
 .../eclipse/cdt/dsf/debug/ui/actions/DsfCommandRunnable.java   | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dsf/org.eclipse.cdt.dsf.ui/src/org/eclipse/cdt/dsf/debug/ui/actions/DsfCommandRunnable.java b/dsf/org.eclipse.cdt.dsf.ui/src/org/eclipse/cdt/dsf/debug/ui/actions/DsfCommandRunnable.java
index 5e0e17dffda..f0e5db0d094 100644
--- a/dsf/org.eclipse.cdt.dsf.ui/src/org/eclipse/cdt/dsf/debug/ui/actions/DsfCommandRunnable.java
+++ b/dsf/org.eclipse.cdt.dsf.ui/src/org/eclipse/cdt/dsf/debug/ui/actions/DsfCommandRunnable.java
@@ -83,8 +83,7 @@ public abstract class DsfCommandRunnable extends DsfRunnable {
     }
 
     /**
-     * Method to perform the actual work.  It should not call monitor.done(), because
-     * it will be called in the super-class.
+     * Method to perform the actual work.
      */
     protected abstract void doExecute();