group-writable). When 'all' (or 'world' or 'everybody'), the
repository will be readable by all users, additionally to being
group-shareable. When 'umask' (or 'false'), git will use permissions
- reported by umask(2). See linkgit:git-init[1]. False by default.
+ reported by umask(2). When '0xxx', where '0xxx' is an octal number,
+ files in the repository will have this mode value. '0xxx' will override
+ user's umask value, and thus, users with a safe umask (0077) can use
+ this option. Examples: '0660' is equivalent to 'group'. '0640' is a
+ repository that is group-readable but not group-writable.
+ See linkgit:git-init[1]. False by default.
core.warnAmbiguousRefs::
If true, git will warn you if the ref name you passed it is ambiguous
designating a single shared repository which people can synchronize with;\r
this document explains how to do that.</p>\r
<p>Some basic familiarity with git is required. This\r
-<a href="tutorial.html">tutorial introduction to git</a> should be sufficient.</p>\r
+<a href="tutorial.html">tutorial introduction to git</a> and the\r
+<a href="glossary.html">git glossary</a> should be sufficient.</p>\r
</div>\r
</div>\r
<h2>Developing against a shared repository</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:51:08 UTC\r
+Last updated 26-Apr-2008 02:23:17 UTC\r
</div>\r
</div>\r
</body>\r
this document explains how to do that.
Some basic familiarity with git is required. This
-link:tutorial.html[tutorial introduction to git] should be sufficient.
+link:tutorial.html[tutorial introduction to git] and the
+link:glossary.html[git glossary] should be sufficient.
Developing against a shared repository
--------------------------------------
group-writable). When <em>all</em> (or <em>world</em> or <em>everybody</em>), the\r
repository will be readable by all users, additionally to being\r
group-shareable. When <em>umask</em> (or <em>false</em>), git will use permissions\r
- reported by umask(2). See <a href="git-init.html">git-init(1)</a>. False by default.\r
+ reported by umask(2). When <em>0xxx</em>, where <em>0xxx</em> is an octal number,\r
+ files in the repository will have this mode value. <em>0xxx</em> will override\r
+ user's umask value, and thus, users with a safe umask (0077) can use\r
+ this option. Examples: <em>0660</em> is equivalent to <em>group</em>. <em>0640</em> is a\r
+ repository that is group-readable but not group-writable.\r
+ See <a href="git-init.html">git-init(1)</a>. False by default.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Apr-2008 00:47:31 UTC\r
+Last updated 26-Apr-2008 02:23:16 UTC\r
</div>\r
</div>\r
</body>\r
the unreferenced loose objects have to be before they are pruned. The\r
default is "2 weeks ago".</p>\r
</div>\r
+<h2>Notes</h2>\r
+<div class="sectionbody">\r
+<p>git-gc tries very hard to be safe about the garbage it collects. In\r
+particular, it will keep not only objects referenced by your current set\r
+of branches and tags, but also objects referenced by the index, remote\r
+tracking branches, refs saved by <a href="git-filter-branch.html">git-filter-branch(1)</a> in\r
+refs/original/, or reflogs (which may references commits in branches\r
+that were later amended or rewound).</p>\r
+<p>If you are expecting some objects to be collected and they aren't, check\r
+all of those locations and decide whether it makes sense in your case to\r
+remove those references.</p>\r
+</div>\r
<h2>See Also</h2>\r
<div class="sectionbody">\r
<p><a href="git-prune.html">git-prune(1)</a>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 20-Mar-2008 08:45:34 UTC\r
+Last updated 26-Apr-2008 02:23:16 UTC\r
</div>\r
</div>\r
</body>\r
the unreferenced loose objects have to be before they are pruned. The
default is "2 weeks ago".
+
+Notes
+-----
+
+git-gc tries very hard to be safe about the garbage it collects. In
+particular, it will keep not only objects referenced by your current set
+of branches and tags, but also objects referenced by the index, remote
+tracking branches, refs saved by linkgit:git-filter-branch[1] in
+refs/original/, or reflogs (which may references commits in branches
+that were later amended or rewound).
+
+If you are expecting some objects to be collected and they aren't, check
+all of those locations and decide whether it makes sense in your case to
+remove those references.
+
See Also
--------
linkgit:git-prune[1]
extensible.</p>\r
</dd>\r
<dt>\r
---shared[={false|true|umask|group|all|world|everybody}]\r
+--shared[={false|true|umask|group|all|world|everybody|0xxx}]\r
</dt>\r
<dd>\r
<p>\r
<em>all</em> (or <em>world</em> or <em>everybody</em>): Same as <em>group</em>, but make the repository\r
readable by all users.\r
</p>\r
+</li>\r
+<li>\r
+<p>\r
+<em>0xxx</em>: <em>0xxx</em> is an octal number and each file will have mode <em>0xxx</em>\r
+ Any option except <em>umask</em> can be set using this option. <em>0xxx</em> will\r
+ override users umask(2) value, and thus, users with a safe umask (0077)\r
+ can use this option. <em>0640</em> will create a repository which is group-readable\r
+ but not writable. <em>0660</em> is equivalent to <em>group</em>.\r
+</p>\r
<p>By default, the configuration flag receive.denyNonFastForwards is enabled\r
in shared repositories, so that you cannot force a non fast-forwarding push\r
into it.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:27 UTC\r
+Last updated 26-Apr-2008 02:23:17 UTC\r
</div>\r
</div>\r
</body>\r
"hook" files. The suggested patterns and hook files are all modifiable and
extensible.
---shared[={false|true|umask|group|all|world|everybody}]::
+--shared[={false|true|umask|group|all|world|everybody|0xxx}]::
Specify that the git repository is to be shared amongst several users. This
allows users belonging to the same group to push into that
- 'all' (or 'world' or 'everybody'): Same as 'group', but make the repository
readable by all users.
+ - '0xxx': '0xxx' is an octal number and each file will have mode '0xxx'
+ Any option except 'umask' can be set using this option. '0xxx' will
+ override users umask(2) value, and thus, users with a safe umask (0077)
+ can use this option. '0640' will create a repository which is group-readable
+ but not writable. '0660' is equivalent to 'group'.
+
By default, the configuration flag receive.denyNonFastForwards is enabled
in shared repositories, so that you cannot force a non fast-forwarding push
into it.