From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Mike Hommey <mh@glandium.org>
Cc: Junio C Hamano <junkio@cox.net>,
git discussion list <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update tar.umask default
Date: Wed, 22 Aug 2007 23:03:18 +0200 [thread overview]
Message-ID: <46CCA496.2020101@lsrfire.ath.cx> (raw)
In-Reply-To: <20070821211526.GA12483@glandium.org>
Mike Hommey schrieb:
> Actually, I'd say it's not enough ; users may be confused by the
> sentence just above:
>
> By default, file and directories modes are set to 0666 or 0777 in tar
> archives.
>
> Which is true, but if you are not very familiar with umask, you won't
> actually gather from the rest that the modes are not going to be that by
> default.
Hmm. And I forgot to update two other places. How about this? Too short?
Documentation/config.txt | 14 +++++---------
Documentation/git-archive.txt | 15 ++++++---------
Documentation/git-tar-tree.txt | 15 ++++++---------
3 files changed, 17 insertions(+), 27 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 46f40ad..462595c 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -675,15 +675,11 @@ showbranch.default::
See gitlink:git-show-branch[1].
tar.umask::
- By default, gitlink:git-tar-tree[1] sets file and directories modes
- to 0666 or 0777. While this is both useful and acceptable for projects
- such as the Linux Kernel, it might be excessive for other projects.
- With this variable, it becomes possible to tell
- gitlink:git-tar-tree[1] to apply a specific umask to the modes above.
- The special value "user" indicates that the user's current umask will
- be used. This should be enough for most projects, as it will lead to
- the same permissions as gitlink:git-checkout[1] would use. The default
- value remains 0, which means world read-write.
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) and
+ gitlink:git-archive[1].
user.email::
Your email address to be recorded in any newly created commits.
diff --git a/Documentation/git-archive.txt b/Documentation/git-archive.txt
index 4da07c1..f2080eb 100644
--- a/Documentation/git-archive.txt
+++ b/Documentation/git-archive.txt
@@ -72,16 +72,13 @@ zip
CONFIGURATION
-------------
-By default, file and directories modes are set to 0666 or 0777 in tar
-archives. It is possible to change this by setting the "umask" variable
-in the repository configuration as follows :
-[tar]
- 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.
+tar.umask::
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) for
+ details.
EXAMPLES
--------
diff --git a/Documentation/git-tar-tree.txt b/Documentation/git-tar-tree.txt
index 2d01d96..434607b 100644
--- a/Documentation/git-tar-tree.txt
+++ b/Documentation/git-tar-tree.txt
@@ -42,16 +42,13 @@ OPTIONS
CONFIGURATION
-------------
-By default, file and directories modes are set to 0666 or 0777. It is
-possible to change this by setting the "umask" variable in the
-repository configuration as follows :
-[tar]
- umask = 002 ;# group friendly
-
-The special umask value "user" indicates that the user's current umask
-will be used instead. The default value is 002, which means group
-readable/writable files and directories.
+tar.umask::
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) for
+ details.
EXAMPLES
--------
next prev parent reply other threads:[~2007-08-22 21:04 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 ` [PATCH] Documentation: update tar.umask default René Scharfe
2007-08-21 21:15 ` Mike Hommey
2007-08-22 21:03 ` René Scharfe [this message]
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=46CCA496.2020101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).