diff options
Diffstat (limited to 'man1/git-init.1')
| -rw-r--r-- | man1/git-init.1 | 57 |
1 files changed, 30 insertions, 27 deletions
diff --git a/man1/git-init.1 b/man1/git-init.1 index 5128ee81e..fe2e5b107 100644 --- a/man1/git-init.1 +++ b/man1/git-init.1 @@ -2,12 +2,12 @@ .\" Title: git-init .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 2024-04-05 +.\" Date: 2024-04-09 .\" Manual: Git Manual -.\" Source: Git 2.44.0.501.g19981daefd +.\" Source: Git 2.44.0.548.g91ec36f2cc .\" Language: English .\" -.TH "GIT\-INIT" "1" "2024\-04\-05" "Git 2\&.44\&.0\&.501\&.g19981d" "Git Manual" +.TH "GIT\-INIT" "1" "2024\-04\-09" "Git 2\&.44\&.0\&.548\&.g91ec36" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -32,11 +32,11 @@ git-init \- Create an empty Git repository or reinitialize an existing one .SH "SYNOPSIS" .sp .nf -\fIgit init\fR [\-q | \-\-quiet] [\-\-bare] [\-\-template=<template\-directory>] - [\-\-separate\-git\-dir <git\-dir>] [\-\-object\-format=<format>] - [\-\-ref\-format=<format>] - [\-b <branch\-name> | \-\-initial\-branch=<branch\-name>] - [\-\-shared[=<permissions>]] [<directory>] +\fBgit init\fR [\fB\-q\fR | \fB\-\-quiet\fR] [\fB\-\-bare\fR] [\fB\-\-template=\fR\fI<template\-directory>\fR] + [\fB\-\-separate\-git\-dir\fR \fI<git\-dir>\fR] [\fB\-\-object\-format=\fR\fI<format>\fR] + [\fB\-\-ref\-format=\fR\fI<format>\fR] + [\fB\-b\fR \fI<branch\-name>\fR | \fB\-\-initial\-branch=\fR\fI<branch\-name>\fR] + [\fB\-\-shared\fR[\fB=\fR\fI<permissions>\fR]] [\fI<directory>\fR] .fi .sp .SH "DESCRIPTION" @@ -50,19 +50,19 @@ If the object storage directory is specified via the \fB$GIT_OBJECT_DIRECTORY\fR Running \fBgit init\fR in an existing repository is safe\&. It will not overwrite things that are already there\&. The primary reason for rerunning \fBgit init\fR is to pick up newly added templates (or to move the repository to another place if \fB\-\-separate\-git\-dir\fR is given)\&. .SH "OPTIONS" .PP -\-q, \-\-quiet +\fB\-q\fR, \fB\-\-quiet\fR .RS 4 Only print error and warning messages; all other output will be suppressed\&. .RE .PP -\-\-bare +\fB\-\-bare\fR .RS 4 Create a bare repository\&. If \fBGIT_DIR\fR environment is not set, it is set to the current working directory\&. .RE .PP -\-\-object\-format=<format> +\fB\-\-object\-format=\fR\fI<format>\fR .RS 4 Specify the given object \fI<format>\fR @@ -78,7 +78,7 @@ Note: At present, there is no interoperability between SHA\-256 repositories and .sp Historically, we warned that SHA\-256 repositories may later need backward incompatible changes when we introduce such interoperability features\&. Today, we only expect compatible changes\&. Furthermore, if such changes prove to be necessary, it can be expected that SHA\-256 repositories created with today\(cqs Git will be usable by future versions of Git without data loss\&. .PP -\-\-ref\-format=<format> +\fB\-\-ref\-format=\fR\fI<format>\fR .RS 4 Specify the given ref storage \fI<format>\fR @@ -109,12 +109,12 @@ for the reftable format\&. This format is experimental and its internals are sub .RE .RE .PP -\-\-template=<template\-directory> +\fB\-\-template=\fR\fI<template\-directory>\fR .RS 4 Specify the directory from which templates will be used\&. (See the "TEMPLATE DIRECTORY" section below\&.) .RE .PP -\-\-separate\-git\-dir=<git\-dir> +\fB\-\-separate\-git\-dir=\fR\fI<git\-dir>\fR .RS 4 Instead of initializing the repository as a directory to either \fB$GIT_DIR\fR @@ -124,7 +124,7 @@ or If this is a reinitialization, the repository will be moved to the specified path\&. .RE .PP -\-b <branch\-name>, \-\-initial\-branch=<branch\-name> +\fB\-b\fR \fI<branch\-name>\fR, \fB\-\-initial\-branch=\fR\fI<branch\-name>\fR .RS 4 Use \fI<branch\-name>\fR @@ -134,29 +134,32 @@ for the initial branch in the newly created repository\&. If not specified, fall configuration variable)\&. .RE .PP -\-\-shared[=(false|true|umask|group|all|world|everybody|<perm>)] +\fB\-\-shared\fR[\fB=\fR(\fBfalse\fR|\fBtrue\fR|\fBumask\fR|\fBgroup\fR|\fBall\fR|\fBworld\fR|\fBeverybody\fR|\fI<perm>\fR)] .RS 4 Specify that the Git repository is to be shared amongst several users\&. This allows users belonging to the same group to push into that repository\&. When specified, the config variable \fBcore\&.sharedRepository\fR is set so that files and directories under \fB$GIT_DIR\fR are created with the requested permissions\&. When not specified, Git will use permissions reported by -\fBumask(2)\fR\&. +\fBumask\fR(2)\&. .sp The option can have the following values, defaulting to \fBgroup\fR if no value is given: .PP -umask, false +\fBumask\fR, \fBfalse\fR .RS 4 -Use permissions reported by umask(2)\&. The default, when +Use permissions reported by +\fBumask\fR(2)\&. The default, when \fB\-\-shared\fR is not specified\&. .RE .PP -group, true +\fBgroup\fR, \fBtrue\fR .RS 4 -Make the repository group\-writable, (and g+sx, since the git group may not be the primary group of all users)\&. This is used to loosen the permissions of an otherwise safe umask(2) value\&. Note that the umask still applies to the other permission bits (e\&.g\&. if umask is +Make the repository group\-writable, (and +\fBg+sx\fR, since the git group may not be the primary group of all users)\&. This is used to loosen the permissions of an otherwise safe +\fBumask\fR(2) value\&. Note that the umask still applies to the other permission bits (e\&.g\&. if umask is \fB0022\fR, using \fBgroup\fR will not remove read privileges from other (non\-group) users)\&. See @@ -164,20 +167,20 @@ will not remove read privileges from other (non\-group) users)\&. See for how to exactly specify the repository permissions\&. .RE .PP -all, world, everybody +\fBall\fR, \fBworld\fR, \fBeverybody\fR .RS 4 Same as \fBgroup\fR, but make the repository readable by all users\&. .RE .PP -<perm> +\fI<perm>\fR .RS 4 \fI<perm>\fR is a 3\-digit octal number prefixed with \(oq0` and each file will have mode \fI<perm>\fR\&. \fI<perm>\fR -will override users\(cq\fBumask(2)\fR -value (and not only loosen permissions as +will override users\(cq +\fBumask\fR(2) value (and not only loosen permissions as \fBgroup\fR and \fBall\fR @@ -296,12 +299,12 @@ T} .sp Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there: .PP -init\&.templateDir +\fBinit\&.templateDir\fR .RS 4 Specify the directory from which templates will be copied\&. .RE .PP -init\&.defaultBranch +\fBinit\&.defaultBranch\fR .RS 4 Allows overriding the default branch name e\&.g\&. when initializing a new repository\&. .RE |