<div class="sectionbody">\r
<p><em>git-init-db</em> [--template=<template_directory>] [--shared[=<permissions>]]</p>\r
</div>\r
-<h2>OPTIONS</h2>\r
-<div class="sectionbody">\r
-<dl>\r
-<dt>\r
---template=<template_directory>\r
-</dt>\r
-<dd>\r
-<p>\r
-Provide the directory from which templates will be used. The default template\r
-directory is <tt>/usr/share/git-core/templates</tt>.\r
-</p>\r
-<p>When specified, <tt><template_directory></tt> is used as the source of the template\r
-files rather than the default. The template files include some directory\r
-structure, some suggested "exclude patterns", and copies of non-executing\r
-"hook" files. The suggested patterns and hook files are all modifiable and\r
-extensible.</p>\r
-</dd>\r
-<dt>\r
---shared[={false|true|umask|group|all|world|everybody}]\r
-</dt>\r
-<dd>\r
-<p>\r
-Specify that the git repository is to be shared amongst several users. This\r
-allows users belonging to the same group to push into that\r
-repository. When specified, the config variable "core.sharedRepository" is\r
-set so that files and directories under <tt>$GIT_DIR</tt> are created with the\r
-requested permissions. When not specified, git will use permissions reported\r
-by umask(2).\r
-</p>\r
-<p>The option can have the following values, defaulting to <em>group</em> if no value\r
-is given:</p>\r
-<ul>\r
-<li>\r
-<p>\r
-<em>umask</em> (or <em>false</em>): Use permissions reported by umask(2). The default,\r
- when <tt>--shared</tt> is not specified.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<em>group</em> (or <em>true</em>): Make the repository group-writable, (and g+sx, since\r
- the git group may be not the primary group of all users).\r
-</p>\r
-</li>\r
-<li>\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
-<p>By default, the configuration flag receive.denyNonFastforward is enabled\r
-in shared repositories, so that you cannot force a non fast-forwarding push\r
-into it.</p>\r
-</li>\r
-</ul>\r
-</dd>\r
-</dl>\r
-</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>This command creates an empty git repository - basically a <tt>.git</tt> directory\r
-with subdirectories for <tt>objects</tt>, <tt>refs/heads</tt>, <tt>refs/tags</tt>, and\r
-template files.\r
-An initial <tt>HEAD</tt> file that references the HEAD of the master branch\r
-is also created.</p>\r
-<p>If the <tt>$GIT_DIR</tt> environment variable is set then it specifies a path\r
-to use instead of <tt>./.git</tt> for the base of the repository.</p>\r
-<p>If the object storage directory is specified via the <tt>$GIT_OBJECT_DIRECTORY</tt>\r
-environment variable then the sha1 directories are created underneath -\r
-otherwise the default <tt>$GIT_DIR/objects</tt> directory is used.</p>\r
-<p>Running <tt>git-init-db</tt> in an existing repository is safe. It will not overwrite\r
-things that are already there. The primary reason for rerunning <tt>git-init-db</tt>\r
-is to pick up newly added templates.</p>\r
-<p>Note that <tt>git-init</tt> is the same as <tt>git-init-db</tt>.</p>\r
-</div>\r
-<h2>EXAMPLES</h2>\r
-<div class="sectionbody">\r
-<dl>\r
-<dt>\r
-Start a new git repository for an existing code base\r
-</dt>\r
-<dd>\r
-<div class="listingblock">\r
-<div class="content">\r
-<pre><tt>$ cd /path/to/my/codebase\r
-$ git-init-db <b>(1)</b>\r
-$ git-add . <b>(2)</b></tt></pre>\r
-</div></div>\r
-<ol>\r
-<li>\r
-<p>\r
-prepare /path/to/my/codebase/.git directory\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-add all existing file to the index\r
-</p>\r
-</li>\r
-</ol>\r
-</dd>\r
-</dl>\r
-</div>\r
-<h2>Author</h2>\r
-<div class="sectionbody">\r
-<p>Written by Linus Torvalds <torvalds@osdl.org></p>\r
-</div>\r
-<h2>Documentation</h2>\r
-<div class="sectionbody">\r
-<p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p>\r
-</div>\r
-<h2>GIT</h2>\r
-<div class="sectionbody">\r
-<p>Part of the <a href="git.html">git(7)</a> suite</p>\r
+<p>This is a synonym for <a href="git-init.html">git-init(1)</a>. Please refer to the\r
+documentation of that command.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jan-2007 06:53:18 UTC\r
+Last updated 12-Jan-2007 02:43:35 UTC\r
</div>\r
</div>\r
</body>\r
'git-init-db' [--template=<template_directory>] [--shared[=<permissions>]]
-OPTIONS
--------
-
---
-
---template=<template_directory>::
-
-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.
-
---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).
-
-The option can have the following values, defaulting to 'group' if no value
-is given:
-
- - 'umask' (or 'false'): Use permissions reported by umask(2). The default,
- when `--shared` is not specified.
-
- - 'group' (or 'true'): Make the repository group-writable, (and g+sx, since
- the git group may be not the primary group of all users).
-
- - 'all' (or 'world' or 'everybody'): Same as 'group', 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.
-
---
-
-
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.
-
-If the `$GIT_DIR` environment variable is set then it specifies a path
-to use instead of `./.git` for the base of the repository.
-
-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.
-
-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.
-
-Note that `git-init` is the same as `git-init-db`.
-
-
-EXAMPLES
---------
-
-Start a new git repository for an existing code base::
-+
-----------------
-$ cd /path/to/my/codebase
-$ git-init-db <1>
-$ git-add . <2>
-----------------
-+
-<1> prepare /path/to/my/codebase/.git directory
-<2> add all existing file to the index
-
-
-Author
-------
-Written by Linus Torvalds <torvalds@osdl.org>
-
-Documentation
---------------
-Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
-GIT
----
-Part of the gitlink:git[7] suite
+This is a synonym for gitlink:git-init[1]. Please refer to the
+documentation of that command.
padding-left: 0.5em;\r
}\r
</style>\r
-<title>git-init-db(1)</title>\r
+<title>git-init(1)</title>\r
</head>\r
<body>\r
<div id="header">\r
<h1>\r
-git-init-db(1) Manual Page\r
+git-init(1) Manual Page\r
</h1>\r
<h2>NAME</h2>\r
<div class="sectionbody">\r
-<p>git-init-db -\r
+<p>git-init -\r
Creates an empty git repository\r
</p>\r
</div>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-init-db</em> [--template=<template_directory>] [--shared[=<permissions>]]</p>\r
+<p><em>git-init</em> [--template=<template_directory>] [--shared[=<permissions>]]</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
<p>If the object storage directory is specified via the <tt>$GIT_OBJECT_DIRECTORY</tt>\r
environment variable then the sha1 directories are created underneath -\r
otherwise the default <tt>$GIT_DIR/objects</tt> directory is used.</p>\r
-<p>Running <tt>git-init-db</tt> in an existing repository is safe. It will not overwrite\r
-things that are already there. The primary reason for rerunning <tt>git-init-db</tt>\r
+<p>Running <tt>git-init</tt> in an existing repository is safe. It will not overwrite\r
+things that are already there. The primary reason for rerunning <tt>git-init</tt>\r
is to pick up newly added templates.</p>\r
-<p>Note that <tt>git-init</tt> is the same as <tt>git-init-db</tt>.</p>\r
+<p>Note that <tt>git-init</tt> is the same as <tt>git-init-db</tt>. The command\r
+was primarily meant to initialize the object database, but over\r
+time it has become responsible for setting up the other aspects\r
+of the repository, such as installing the default hooks and\r
+setting the configuration variables. The old name is retained\r
+because people are so used to it and many existing documents\r
+refer to it that way, and this will not change for some time to\r
+come.</p>\r
</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>$ cd /path/to/my/codebase\r
-$ git-init-db <b>(1)</b>\r
+$ git-init <b>(1)</b>\r
$ git-add . <b>(2)</b></tt></pre>\r
</div></div>\r
<ol>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 11-Jan-2007 00:35:44 UTC\r
+Last updated 12-Jan-2007 02:43:35 UTC\r
</div>\r
</div>\r
</body>\r
-include::git-init-db.txt[]
+git-init(1)
+===========
+
+NAME
+----
+git-init - Creates an empty git repository
+
+
+SYNOPSIS
+--------
+'git-init' [--template=<template_directory>] [--shared[=<permissions>]]
+
+
+OPTIONS
+-------
+
+--
+
+--template=<template_directory>::
+
+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.
+
+--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).
+
+The option can have the following values, defaulting to 'group' if no value
+is given:
+
+ - 'umask' (or 'false'): Use permissions reported by umask(2). The default,
+ when `--shared` is not specified.
+
+ - 'group' (or 'true'): Make the repository group-writable, (and g+sx, since
+ the git group may be not the primary group of all users).
+
+ - 'all' (or 'world' or 'everybody'): Same as 'group', 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.
+
+--
+
+
+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.
+
+If the `$GIT_DIR` environment variable is set then it specifies a path
+to use instead of `./.git` for the base of the repository.
+
+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.
+
+Running `git-init` in an existing repository is safe. It will not overwrite
+things that are already there. The primary reason for rerunning `git-init`
+is to pick up newly added templates.
+
+Note that `git-init` is the same as `git-init-db`. The command
+was primarily meant to initialize the object database, but over
+time it has become responsible for setting up the other aspects
+of the repository, such as installing the default hooks and
+setting the configuration variables. The old name is retained
+because people are so used to it and many existing documents
+refer to it that way, and this will not change for some time to
+come.
+
+
+EXAMPLES
+--------
+
+Start a new git repository for an existing code base::
++
+----------------
+$ cd /path/to/my/codebase
+$ git-init <1>
+$ git-add . <2>
+----------------
++
+<1> prepare /path/to/my/codebase/.git directory
+<2> add all existing file to the index
+
+
+Author
+------
+Written by Linus Torvalds <torvalds@osdl.org>
+
+Documentation
+--------------
+Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
+
+GIT
+---
+Part of the gitlink:git[7] suite
+
projects / git.git / commitdiff