Remove dead warning about minUpdaeIndex and maxUpdateIndex affecting refresh

DfsGarbageCollector always performs refreshes.  This warning was from
a prior iteration of the patch set and should have been removed before
the change was merged.

Change-Id: Id4750bb6c1c177e1ef040fd22912f434bbb5e992

org.eclipse.jgit/src/org/eclipse/jgit/internal/storage/dfs/DfsGarbageCollector.java

@@ -173,11 +173,6 @@ public class DfsGarbageCollector {
 
 	/**
 	 * Set minUpdateIndex for the initial reftable created during conversion.
-	 * <p>
-	 * <b>Warning:</b> A setting {@code != 1} <b>disables cache refreshes</b>
-	 * normally performed at the start of {@link #pack(ProgressMonitor)}.
-	 * Callers must ensure the reference cache is current and will have been
-	 * read before the pack list.
 	 *
 	 * @param u
 	 *            minUpdateIndex for the initial reftable created by scanning
@@ -193,11 +188,6 @@ public class DfsGarbageCollector {
 
 	/**
 	 * Set maxUpdateIndex for the initial reftable created during conversion.
-	 * <p>
-	 * <b>Warning:</b> A setting {@code != 1} <b>disables cache refreshes</b>
-	 * normally performed at the start of {@link #pack(ProgressMonitor)}.
-	 * Callers must ensure the reference cache is current and will have been
-	 * read before the pack list.
 	 *
 	 * @param u
 	 *            maxUpdateIndex for the initial reftable created by scanning