From d39df714546981cadedafb00760f3045e2530ed2 Mon Sep 17 00:00:00 2001
From: Stefan Bodewig <bodewig@apache.org>
Date: Tue, 27 Oct 2009 17:44:22 +0000
Subject: [PATCH] explicitly state that tar doesn't even try to preserve
 existing permissions

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@830262 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/CoreTasks/tar.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/manual/CoreTasks/tar.html b/docs/manual/CoreTasks/tar.html
index 29a3d4572..d2ae20b5c 100644
--- a/docs/manual/CoreTasks/tar.html
+++ b/docs/manual/CoreTasks/tar.html
@@ -38,7 +38,9 @@ set of files to be included in the implicit fileset.</p>
       resource collections and a special form of filesets. These
 filesets are extended to allow control over the access mode, username and groupname
 to be applied to the tar entries. This is useful, for example, when preparing archives for
-Unix systems where some files need to have execute permission.</p>
+  Unix systems where some files need to have execute permission.  By
+  default this task will use Unix permissions of 644 for files and 755
+  for directories.</p>
 
 <p>Early versions of tar did not support path lengths greater than 100
 characters. Modern versions of tar do so, but in incompatible ways.