From: Junio C Hamano Date: Sat, 26 Apr 2008 02:23:37 +0000 (+0000) Subject: Autogenerated HTML docs for v1.5.5.1-89-g36c79 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=2f102bb1f5361354dc6678e045bbc8fd103136e5;p=git.git Autogenerated HTML docs for v1.5.5.1-89-g36c79 --- diff --git a/config.txt b/config.txt index fe43b1257..7a24f6e81 100644 --- a/config.txt +++ b/config.txt @@ -261,7 +261,12 @@ core.sharedRepository:: 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 diff --git a/cvs-migration.html b/cvs-migration.html index ed06578d3..69224bb54 100644 --- a/cvs-migration.html +++ b/cvs-migration.html @@ -269,7 +269,8 @@ important than any other. However, you can emulate the CVS model by designating a single shared repository which people can synchronize with; this document explains how to do that.

Some basic familiarity with git is required. This -tutorial introduction to git should be sufficient.

+tutorial introduction to git and the +git glossary should be sufficient.

Developing against a shared repository

@@ -416,7 +417,7 @@ repositories without the need for a central maintainer.

diff --git a/cvs-migration.txt b/cvs-migration.txt index ea9890022..00f2e36b2 100644 --- a/cvs-migration.txt +++ b/cvs-migration.txt @@ -8,7 +8,8 @@ designating a single shared repository which people can synchronize with; 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 -------------------------------------- diff --git a/git-config.html b/git-config.html index ecabd61ba..78ca9551d 100644 --- a/git-config.html +++ b/git-config.html @@ -1013,7 +1013,12 @@ core.sharedRepository 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 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 git-init(1). False by default.

@@ -2417,7 +2422,7 @@ web.browser diff --git a/git-gc.html b/git-gc.html index 35756909b..ca48034f2 100644 --- a/git-gc.html +++ b/git-gc.html @@ -374,6 +374,18 @@ more details. This defaults to 10.

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 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

git-prune(1) @@ -391,7 +403,7 @@ default is "2 weeks ago".

diff --git a/git-gc.txt b/git-gc.txt index d424a4ecb..b6b5ce151 100644 --- a/git-gc.txt +++ b/git-gc.txt @@ -104,6 +104,21 @@ The optional configuration variable 'gc.pruneExpire' controls how old 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] diff --git a/git-init.html b/git-init.html index f75994ee9..ab6a6303f 100644 --- a/git-init.html +++ b/git-init.html @@ -300,7 +300,7 @@ structure, some suggested "exclude patterns", and copies of non-executing extensible.

---shared[={false|true|umask|group|all|world|everybody}] +--shared[={false|true|umask|group|all|world|everybody|0xxx}]

@@ -331,6 +331,15 @@ is given:

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.

    @@ -403,7 +412,7 @@ add all existing file to the index diff --git a/git-init.txt b/git-init.txt index 62914da97..b17ae8485 100644 --- a/git-init.txt +++ b/git-init.txt @@ -31,7 +31,7 @@ structure, some suggested "exclude patterns", and copies of non-executing "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 @@ -52,6 +52,12 @@ is given: - '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.