From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <junkio@cox.net>
Cc: Mike Hommey <mh@glandium.org>, git discussion list <git@vger.kernel.org>
Subject: [PATCH] Documentation: update tar.umask default
Date: Tue, 21 Aug 2007 20:01:16 +0200 [thread overview]
Message-ID: <46CB286C.8000403@lsrfire.ath.cx> (raw)
In-Reply-To: <20070820174142.GA7943@glandium.org>
As noted by Mike Hommey, the documentation for the config setting tar.umask
is not up-to-date. Commit f08b3b0e2e9ad87767d80ff03b013c686e08ba4b changed
the default from 0 to 2; this patch finally documents it.
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
---
diff --git a/Documentation/git-archive.txt b/Documentation/git-archive.txt
index 4da07c1..9984a11 100644
--- a/Documentation/git-archive.txt
+++ b/Documentation/git-archive.txt
@@ -80,8 +80,8 @@ in the repository configuration as follows :
umask = 002 ;# group friendly
The special umask value "user" indicates that the user's current umask
-will be used instead. The default value remains 0, which means world
-readable/writable files and directories.
+will be used instead. The default is 002, which allows reading for all
+and writing for both owner and group.
EXAMPLES
--------
next prev parent reply other threads:[~2007-08-21 18:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:44 confused about preserved permissions martin f krafft
2007-08-20 16:54 ` Pierre Habouzit
2007-08-20 17:38 ` martin f krafft
2007-08-20 17:41 ` Mike Hommey
2007-08-20 17:58 ` David Kastrup
2007-08-20 18:13 ` Mike Hommey
2007-08-20 18:44 ` David Kastrup
[not found] ` <86zm0mgicy.fsf@lola.quinscape.zz>
2007-08-20 18:48 ` Mike Hommey
2007-08-20 19:43 ` Jan Hudec
2007-08-20 19:50 ` Mike Hommey
2007-08-20 20:07 ` Alex Riesen
2007-08-20 20:10 ` Mike Hommey
2007-08-20 20:27 ` Jan Hudec
2007-08-20 20:42 ` David Kastrup
2007-08-20 20:44 ` Mike Hommey
2007-08-20 20:08 ` Jan Hudec
2007-08-20 20:39 ` David Kastrup
2007-08-20 20:50 ` Mike Hommey
2007-08-20 21:03 ` David Kastrup
2007-08-21 1:35 ` Shawn O. Pearce
2007-08-21 2:06 ` Junio C Hamano
2007-08-21 5:34 ` Mike Hommey
2007-08-21 6:04 ` David Kastrup
2007-08-21 18:01 ` René Scharfe
2007-08-21 18:01 ` René Scharfe [this message]
2007-08-21 21:15 ` [PATCH] Documentation: update tar.umask default Mike Hommey
2007-08-22 21:03 ` René Scharfe
2007-08-20 18:35 ` confused about preserved permissions Alex Riesen
2007-08-22 12:18 ` Benoit SIGOURE
2007-08-22 12:52 ` Johannes Sixt
2007-08-22 22:09 ` Junio C Hamano
2007-08-23 6:00 ` martin f krafft
2007-08-23 6:12 ` David Kastrup
2007-08-23 6:23 ` martin f krafft
2007-08-23 7:48 ` Benoit SIGOURE
2007-08-23 7:57 ` Junio C Hamano
2007-08-23 8:08 ` David Kastrup
2007-09-03 18:59 ` Jan Hudec
2007-08-23 7:03 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CB286C.8000403@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mh@glandium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.