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 gitlink:git-init-db[1]. False by default.
+ reported by umask(2). See gitlink:git-init[1]. False by default.
core.warnAmbiguousRefs::
If true, git will warn you if the ref name you passed it is ambiguous
<p>For our first example, we're going to start a totally new repository from\r
scratch, with no pre-existing files, and we'll call it <tt>git-tutorial</tt>.\r
To start up, create a subdirectory for it, change into that\r
-subdirectory, and initialize the git infrastructure with <tt>git-init-db</tt>:</p>\r
+subdirectory, and initialize the git infrastructure with <tt>git-init</tt>:</p>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>$ mkdir git-tutorial\r
$ cd git-tutorial\r
-$ git-init-db</tt></pre>\r
+$ git-init</tt></pre>\r
</div></div>\r
<p>to which git will reply</p>\r
<div class="listingblock">\r
<pre><tt>$ mkdir my-git.git</tt></pre>\r
</div></div>\r
<p>Then, make that directory into a git repository by running\r
-<tt>git init-db</tt>, but this time, since its name is not the usual\r
+<tt>git init</tt>, but this time, since its name is not the usual\r
<tt>.git</tt>, we do things slightly differently:</p>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>$ GIT_DIR=my-git.git git-init-db</tt></pre>\r
+<pre><tt>$ GIT_DIR=my-git.git git-init</tt></pre>\r
</div></div>\r
<p>Make sure this directory is available for others you want your\r
changes to be pulled by via the transport of your choice. Also\r
</p>\r
<p>If other people are pulling from your repository over dumb\r
transport protocols (HTTP), you need to keep this repository\r
-<em>dumb transport friendly</em>. After <tt>git init-db</tt>,\r
+<em>dumb transport friendly</em>. After <tt>git init</tt>,\r
<tt>$GIT_DIR/hooks/post-update</tt> copied from the standard templates\r
would contain a call to <tt>git-update-server-info</tt> but the\r
<tt>post-update</tt> hook itself is disabled by default — enable it\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Dec-2006 07:43:55 UTC\r
+Last updated 13-Jan-2007 08:09:05 UTC\r
</div>\r
</div>\r
</body>\r
For our first example, we're going to start a totally new repository from
scratch, with no pre-existing files, and we'll call it `git-tutorial`.
To start up, create a subdirectory for it, change into that
-subdirectory, and initialize the git infrastructure with `git-init-db`:
+subdirectory, and initialize the git infrastructure with `git-init`:
------------------------------------------------
$ mkdir git-tutorial
$ cd git-tutorial
-$ git-init-db
+$ git-init
------------------------------------------------
to which git will reply
------------
Then, make that directory into a git repository by running
-`git init-db`, but this time, since its name is not the usual
+`git init`, but this time, since its name is not the usual
`.git`, we do things slightly differently:
------------
-$ GIT_DIR=my-git.git git-init-db
+$ GIT_DIR=my-git.git git-init
------------
Make sure this directory is available for others you want your
+
If other people are pulling from your repository over dumb
transport protocols (HTTP), you need to keep this repository
-'dumb transport friendly'. After `git init-db`,
+'dumb transport friendly'. After `git init`,
`$GIT_DIR/hooks/post-update` copied from the standard templates
would contain a call to `git-update-server-info` but the
`post-update` hook itself is disabled by default -- enable it
<div class="content">\r
<pre><tt>$ mkdir /pub/my-repo.git\r
$ cd /pub/my-repo.git\r
-$ git --bare init-db --shared\r
+$ git --bare init --shared\r
$ git --bare fetch /home/alice/myproject master:master</tt></pre>\r
</div></div>\r
<p>Next, give every team member read/write access to this repository. One\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 01-Jan-2007 03:20:16 UTC\r
+Last updated 13-Jan-2007 08:09:07 UTC\r
</div>\r
</div>\r
</body>\r
------------------------------------------------
$ mkdir /pub/my-repo.git
$ cd /pub/my-repo.git
-$ git --bare init-db --shared
+$ git --bare init --shared
$ git --bare fetch /home/alice/myproject master:master
------------------------------------------------
</dt>\r
<dd>\r
<p>\r
- By default, the command looks for suspicious lines the\r
- commit introduces, and aborts committing if there is one.\r
- The definition of <em>suspicious lines</em> is currently the\r
- lines that has trailing whitespaces, and the lines whose\r
- indentation has a SP character immediately followed by a\r
- TAB character. This option turns off the check.\r
+ This option bypasses the pre-commit hook.\r
+ See also <a href="hooks.html">hooks</a>.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 31-Dec-2006 01:19:02 UTC\r
+Last updated 13-Jan-2007 08:09:00 UTC\r
</div>\r
</div>\r
</body>\r
Add Signed-off-by line at the end of the commit message.
--no-verify::
- By default, the command looks for suspicious lines the
- commit introduces, and aborts committing if there is one.
- The definition of 'suspicious lines' is currently the
- lines that has trailing whitespaces, and the lines whose
- indentation has a SP character immediately followed by a
- TAB character. This option turns off the check.
+ This option bypasses the pre-commit hook.
+ See also link:hooks.html[hooks].
-e|--edit::
The message taken from file with `-F`, command line with
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
+for backward compatibility reasons.</p>\r
</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Jan-2007 02:43:35 UTC\r
+Last updated 13-Jan-2007 08:09:00 UTC\r
</div>\r
</div>\r
</body>\r
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.
+for backward compatibility reasons.
EXAMPLES
<div class="content">\r
<pre><tt>$ mkdir -p /home/sean/import/jam\r
$ cd /home/sean/import/jam\r
-$ git init-db\r
+$ git init\r
$ git p4import //public/jam jammy</tt></pre>\r
</div></div>\r
</div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:15 UTC\r
+Last updated 13-Jan-2007 08:09:01 UTC\r
</div>\r
</div>\r
</body>\r
------------
$ mkdir -p /home/sean/import/jam
$ cd /home/sean/import/jam
-$ git init-db
+$ git init
$ git p4import //public/jam jammy
------------
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-prune-packed</em> [-n]</p>\r
+<p><em>git-prune-packed</em> [-n] [-q]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
removed.\r
</p>\r
</dd>\r
+<dt>\r
+-q\r
+</dt>\r
+<dd>\r
+<p>\r
+ Squelch the progress indicator.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>Author</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:17 UTC\r
+Last updated 13-Jan-2007 08:09:01 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-prune-packed' [-n]
+'git-prune-packed' [-n] [-q]
DESCRIPTION
Don't actually remove any objects, only show those that would have been
removed.
+-q::
+ Squelch the progress indicator.
+
Author
------
Written by Linus Torvalds <torvalds@osdl.org>
group-writable). When <em>all</em> (or <em>world</em> or <em>everybody</em>), the\r
repository will be readable by all users, additionally to being\r
group-shareable. When <em>umask</em> (or <em>false</em>), git will use permissions\r
- reported by umask(2). See <a href="git-init-db.html">git-init-db(1)</a>. False by default.\r
+ reported by umask(2). See <a href="git-init.html">git-init(1)</a>. False by default.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jan-2007 06:53:19 UTC\r
+Last updated 13-Jan-2007 08:09:02 UTC\r
</div>\r
</div>\r
</body>\r
<dd>\r
<p>\r
Only used with the <em>init</em> command.\r
- These are passed directly to <a href="git-init-db.html">git-init-db(1)</a>.\r
+ These are passed directly to <a href="git-init.html">git-init(1)</a>.\r
</p>\r
</dd>\r
<dt>\r
<p>Tracking and contributing to a the trunk of a Subversion-managed project:</p>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt># Initialize a repo (like git init-db):\r
+<pre><tt># Initialize a repo (like git init):\r
git-svn init http://svn.foo.org/project/trunk\r
# Fetch remote revisions:\r
git-svn fetch\r
<em><a href="#tracking-multiple-repos">Tracking Multiple Repositories or Branches</a></em></p>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt># Initialize a repo (like git init-db):\r
+<pre><tt># Initialize a repo (like git init):\r
git-svn multi-init http://svn.foo.org/project \\r
-T trunk -b branches -t tags\r
# Fetch remote revisions:\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Jan-2007 05:05:02 UTC\r
+Last updated 13-Jan-2007 08:09:03 UTC\r
</div>\r
</div>\r
</body>\r
--shared::
--template=<template_directory>::
Only used with the 'init' command.
- These are passed directly to gitlink:git-init-db[1].
+ These are passed directly to gitlink:git-init[1].
-r <ARG>::
--revision <ARG>::
Tracking and contributing to a the trunk of a Subversion-managed project:
------------------------------------------------------------------------
-# Initialize a repo (like git init-db):
+# Initialize a repo (like git init):
git-svn init http://svn.foo.org/project/trunk
# Fetch remote revisions:
git-svn fetch
'<<tracking-multiple-repos,Tracking Multiple Repositories or Branches>>'
------------------------------------------------------------------------
-# Initialize a repo (like git init-db):
+# Initialize a repo (like git init):
git-svn multi-init http://svn.foo.org/project \
-T trunk -b branches -t tags
# Fetch remote revisions:
<dt>\r
<a href="git-init.html">git-init(1)</a>\r
</dt>\r
-<dt>\r
-<a href="git-init-db.html">git-init-db(1)</a>\r
-</dt>\r
<dd>\r
<p>\r
- Creates an empty git object database, or reinitialize an\r
+ Creates an empty git repository, or reinitialize an\r
existing one.\r
</p>\r
</dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jan-2007 06:53:21 UTC\r
+Last updated 13-Jan-2007 08:09:04 UTC\r
</div>\r
</div>\r
</body>\r
Build pack idx file for an existing packed archive.
gitlink:git-init[1]::
-gitlink:git-init-db[1]::
- Creates an empty git object database, or reinitialize an
+ Creates an empty git repository, or reinitialize an
existing one.
gitlink:git-merge-file[1]::
<a href="#ref_branch">branch</a> <a href="#ref_head">head</a>". And <tt>git <a href="#ref_push">push</a>\r
$URL refs/heads/<a href="#ref_master">master</a>:refs/heads/to-upstream</tt> means\r
"publish my <a href="#ref_master">master</a> <a href="#ref_branch">branch</a>\r
- <a href="#ref_head">head</a> as to-upstream <a href="#ref_master">master</a> <a href="#ref_head">head</a>\r
- at $URL". See also <a href="git-push.html">git-push(1)</a>\r
+ <a href="#ref_head">head</a> as to-upstream <a href="#ref_branch">branch</a> at $URL". See\r
+ also <a href="git-push.html">git-push(1)</a>\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jan-2007 06:53:26 UTC\r
+Last updated 13-Jan-2007 08:09:09 UTC\r
</div>\r
</div>\r
</body>\r
means "grab the master branch head from the $URL and store
it as my origin branch head".
And `git push $URL refs/heads/master:refs/heads/to-upstream`
- means "publish my master branch head as to-upstream master head
+ means "publish my master branch head as to-upstream branch
at $URL". See also gitlink:git-push[1]
repository::
<div class="sectionbody">\r
<p>Hooks are little scripts you can place in <tt>$GIT_DIR/hooks</tt>\r
directory to trigger action at certain points. When\r
-<tt>git-init-db</tt> is run, a handful example hooks are copied in the\r
+<tt>git-init</tt> is run, a handful example hooks are copied in the\r
<tt>hooks</tt> directory of the new repository, but by default they are\r
all disabled. To enable a hook, make it executable with <tt>chmod +x</tt>.</p>\r
<p>This document describes the currently defined hooks.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 01-Jan-2007 03:20:17 UTC\r
+Last updated 13-Jan-2007 08:09:09 UTC\r
</div>\r
</div>\r
</body>\r
Hooks are little scripts you can place in `$GIT_DIR/hooks`
directory to trigger action at certain points. When
-`git-init-db` is run, a handful example hooks are copied in the
+`git-init` is run, a handful example hooks are copied in the
`hooks` directory of the new repository, but by default they are
all disabled. To enable a hook, make it executable with `chmod +x`.
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:46 UTC\r
+Last updated 13-Jan-2007 08:09:08 UTC\r
</div>\r
</div>\r
</body>\r
Initialize a bare repository
$ cd my-new-repo.git
- $ git --bare init-db
+ $ git --bare init
Change the ownership to your web-server's credentials. Use "grep ^User
<p>\r
Hooks are customization scripts used by various git\r
commands. A handful of sample hooks are installed when\r
- <tt>git init-db</tt> is run, but all of them are disabled by\r
+ <tt>git init</tt> is run, but all of them are disabled by\r
default. To enable, they need to be made executable.\r
Read <a href="hooks.html">hooks</a> for more details about\r
each hook.\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 20-Nov-2006 03:17:36 UTC\r
+Last updated 13-Jan-2007 08:09:08 UTC\r
</div>\r
</div>\r
</body>\r
hooks::
Hooks are customization scripts used by various git
commands. A handful of sample hooks are installed when
- `git init-db` is run, but all of them are disabled by
+ `git init` is run, but all of them are disabled by
default. To enable, they need to be made executable.
Read link:hooks.html[hooks] for more details about
each hook.