.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-INIT\-DB" "1" "10/03/2006" "" ""
+.TH "GIT\-INIT\-DB" "1" "01/08/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
git\-init\-db \- Creates an empty git repository
.SH "SYNOPSIS"
\fIgit\-init\-db\fR [\-\-template=<template_directory>] [\-\-shared[=<permissions>]]
-.sp
.SH "OPTIONS"
.TP
\-\-template=<template_directory>
-Provide the directory from which templates will be used. The default template directory is
-/usr/share/git\-core/templates.
-.sp
-When specified,
-<template_directory>
-is used as the source of the template files rather than the default. The template files include some directory structure, some suggested "exclude patterns", and copies of non\-executing "hook" files. The suggested patterns and hook files are all modifiable and extensible.
+Provide the directory from which templates will be used. The default template directory is /usr/share/git\-core/templates.
+
+When specified, <template_directory> is used as the source of the template files rather than the default. The template files include some directory structure, some suggested "exclude patterns", and copies of non\-executing "hook" files. The suggested patterns and hook files are all modifiable and extensible.
.TP
\-\-shared[={false|true|umask|group|all|world|everybody}]
-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 "core.sharedRepository" is set so that files and directories under
-$GIT_DIR
-are created with the requested permissions. When not specified, git will use permissions reported by umask(2).
-.sp
-The option can have the following values, defaulting to
-\fIgroup\fR
-if no value is given:
+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 "core.sharedRepository" is set so that files and directories under $GIT_DIR are created with the requested permissions. When not specified, git will use permissions reported by umask(2).
+
+The option can have the following values, defaulting to \fIgroup\fR if no value is given:
.RS
.TP 3
\(bu
-\fIumask\fR
-(or
-\fIfalse\fR): Use permissions reported by umask(2). The default, when
-\-\-shared
-is not specified.
+\fIumask\fR (or \fIfalse\fR): Use permissions reported by umask(2). The default, when \-\-shared is not specified.
.TP
\(bu
-\fIgroup\fR
-(or
-\fItrue\fR): Make the repository group\-writable, (and g+sx, since the git group may be not the primary group of all users).
+\fIgroup\fR (or \fItrue\fR): Make the repository group\-writable, (and g+sx, since the git group may be not the primary group of all users).
.TP
\(bu
-\fIall\fR
-(or
-\fIworld\fR
-or
-\fIeverybody\fR): Same as
-\fIgroup\fR, but make the repository readable by all users.
-.sp
+\fIall\fR (or \fIworld\fR or \fIeverybody\fR): Same as \fIgroup\fR, but make the repository readable by all users.
+
By default, the configuration flag receive.denyNonFastforward is enabled in shared repositories, so that you cannot force a non fast\-forwarding push into it.
.RE
.SH "DESCRIPTION"
This command creates an empty git repository \- basically a .git directory with subdirectories for objects, refs/heads, refs/tags, and template files. An initial HEAD file that references the HEAD of the master branch is also created.
-.sp
+
If the $GIT_DIR environment variable is set then it specifies a path to use instead of ./.git for the base of the repository.
-.sp
+
If the object storage directory is specified via the $GIT_OBJECT_DIRECTORY environment variable then the sha1 directories are created underneath \- otherwise the default $GIT_DIR/objects directory is used.
-.sp
+
Running git\-init\-db in an existing repository is safe. It will not overwrite things that are already there. The primary reason for rerunning git\-init\-db is to pick up newly added templates.
-.sp
+
+Note that git\-init is the same as git\-init\-db.
.SH "EXAMPLES"
.TP
Start a new git repository for an existing code base
.br
.SH "AUTHOR"
Written by Linus Torvalds <torvalds@osdl.org>
-.sp
.SH "DOCUMENTATION"
Documentation by David Greaves, Junio C Hamano and the git\-list <git@vger.kernel.org>.
-.sp
.SH "GIT"
Part of the \fBgit\fR(7) suite
-.sp
+
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-REPO\-CONFIG" "1" "01/03/2007" "" ""
+.TH "GIT\-REPO\-CONFIG" "1" "01/08/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
core.legacyheaders
A boolean which enables the legacy object header format in case you want to interoperate with old clients accessing the object database directly (where the "http://" and "rsync://" protocols count as direct access).
.TP
+core.packedGitWindowSize
+Number of bytes of a pack file to map into memory in a single mapping operation. Larger window sizes may allow your system to process a smaller number of large pack files more quickly. Smaller window sizes will negatively affect performance due to increased calls to the operating system's memory manager, but may improve performance when accessing a large number of large pack files.
+
+Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should be reasonable for all users/operating systems. You probably do not need to adjust this value.
+
+Common unit suffixes of \fIk\fR, \fIm\fR, or \fIg\fR are supported.
+.TP
+core.packedGitLimit
+Maximum number of bytes to map simultaneously into memory from pack files. If Git needs to access more than this many bytes at once to complete an operation it will unmap existing regions to reclaim virtual address space within the process.
+
+Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. This should be reasonable for all users/operating systems, except on the largest projects. You probably do not need to adjust this value.
+
+Common unit suffixes of \fIk\fR, \fIm\fR, or \fIg\fR are supported.
+.TP
alias.*
Command aliases for the \fBgit\fR(1) command wrapper \- e.g. after defining "alias.last = cat\-file commit HEAD", the invocation "git last" is equivalent to "git cat\-file commit HEAD". To avoid confusion and troubles with script usage, aliases that hide existing git commands are ignored. Arguments are split by spaces, the usual shell quoting and escaping is supported. quote pair and a backslash can be used to quote them.
.TP
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SVN" "1" "01/07/2007" "" ""
+.TH "GIT\-SVN" "1" "01/08/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fImulti\-init\fR
This command supports git\-svnimport\-like command\-line syntax for importing repositories that are layed out as recommended by the SVN folks. This is a bit more tolerant than the git\-svnimport command\-line syntax and doesn't require the user to figure out where the repository URL ends and where the repository path begins.
.TP
+\-T<trunk_subdir> , \-\-trunk=<trunk_subdir> , \-t<tags_subdir> , \-\-tags=<tags_subdir> , \-b<branches_subdir> , \-\-branches=<branches_subdir>
+These are the command\-line options for multi\-init. Each of these flags can point to a relative repository path (\-\-tags=project/tags') or a full url (\-\-tags=https://foo.org/project/tags)
+
+\-\-prefix=<prefix> This allows one to specify a prefix which is prepended to the names of remotes. The prefix does not automatically include a trailing slash, so be sure you include one in the argument if that is what you want. This is useful if you wish to track multiple projects that share a common repository.
+.TP
\fImulti\-fetch\fR
This runs fetch on all known SVN branches we're tracking. This will NOT discover new branches (unlike git\-svnimport), so multi\-init will need to be re\-run (it's idempotent).
.SH "OPTIONS"
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "12/28/2006" "" ""
+.TH "GIT" "7" "01/08/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fBgit\-index\-pack\fR(1)
Build pack idx file for an existing packed archive.
.TP
-\fBgit\-init\-db\fR(1)
+\fBgit\-init\fR(1) , \fBgit\-init\-db\fR(1)
Creates an empty git object database, or reinitialize an existing one.
.TP
\fBgit\-merge\-file\fR(1)
projects / git.git / commitdiff