From: Junio C Hamano Date: Fri, 12 Jan 2007 02:43:42 +0000 (+0000) Subject: Autogenerated HTML docs for v1.5.0-rc1 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=91f77a0d717f22a5e0b1c474ee9b8db28fa0e0ca;p=git.git Autogenerated HTML docs for v1.5.0-rc1 --- diff --git a/git-init-db.html b/git-init-db.html index a9aa49c55..1f1bd2913 100644 --- a/git-init-db.html +++ b/git-init-db.html @@ -274,123 +274,14 @@ git-init-db(1) Manual Page

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

    -add all existing file to the index -

    -
    3. -
-
-
-
-

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 git(7) suite

+

This is a synonym for git-init(1). Please refer to the +documentation of that command.

diff --git a/git-init-db.txt b/git-init-db.txt index bc3ba1493..5412135d7 100644 --- a/git-init-db.txt +++ b/git-init-db.txt @@ -11,96 +11,9 @@ SYNOPSIS 'git-init-db' [--template=] [--shared[=]] -OPTIONS -------- - --- - ---template=:: - -Provide the directory from which templates will be used. The default template -directory is `/usr/share/git-core/templates`. - -When specified, `` 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 - -Documentation --------------- -Documentation by David Greaves, Junio C Hamano and the git-list . -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. diff --git a/git-init.html b/git-init.html index 6bc5b1f9b..b400c4a25 100644 --- a/git-init.html +++ b/git-init.html @@ -256,23 +256,23 @@ div.exampleblock-content { padding-left: 0.5em; } -git-init-db(1) +git-init(1)

SYNOPSIS

-

git-init-db [--template=<template_directory>] [--shared[=<permissions>]]

+

git-init [--template=<template_directory>] [--shared[=<permissions>]]

OPTIONS

@@ -343,10 +343,17 @@ 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 +

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.

+

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

@@ -358,7 +365,7 @@ Start a new git repository for an existing code base 
$ cd /path/to/my/codebase
-$ git-init-db   (1)
+$ git-init      (1)
 $ git-add .     (2)
    @@ -390,7 +397,7 @@ add all existing file to the index
diff --git a/git-init.txt b/git-init.txt index 36838c753..e1fd6884f 100644 --- a/git-init.txt +++ b/git-init.txt @@ -1 +1,113 @@ -include::git-init-db.txt[] +git-init(1) +=========== + +NAME +---- +git-init - Creates an empty git repository + + +SYNOPSIS +-------- +'git-init' [--template=] [--shared[=]] + + +OPTIONS +------- + +-- + +--template=:: + +Provide the directory from which templates will be used. The default template +directory is `/usr/share/git-core/templates`. + +When specified, `` 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 + +Documentation +-------------- +Documentation by David Greaves, Junio C Hamano and the git-list . + +GIT +--- +Part of the gitlink:git[7] suite +