Autogenerated HTML docs for v2.44.0-325-g11c82

1 files changed, 37 insertions, 26 deletions

diff --git a/git-init.html b/git-init.html
index d289f2584..51c139e95 100644
--- a/git-init.html
+++ b/git-init.html
@@ -772,10 +772,10 @@ to use instead of <code>./.git</code> for the base of the repository.</p></div>
 <code>$GIT_OBJECT_DIRECTORY</code> environment variable then the sha1 directories

 are created underneath; otherwise, the default <code>$GIT_DIR/objects</code>

 directory is used.</p></div>

-<div class="paragraph"><p>Running <em>git init</em> in an existing repository is safe. It will not

+<div class="paragraph"><p>Running <code>git init</code> in an existing repository is safe. It will not

 overwrite things that are already there. The primary reason for

-rerunning <em>git init</em> is to pick up newly added templates (or to move

-the repository to another place if --separate-git-dir is given).</p></div>

+rerunning <code>git init</code> is to pick up newly added templates (or to move

+the repository to another place if <code>--separate-git-dir</code> is given).</p></div>

 </div>

 </div>

 <div class="sect1">

@@ -807,8 +807,8 @@ current working directory.
 </dt>

 <dd>

 <p>

-Specify the given object format (hash algorithm) for the repository.  The valid

-values are <em>sha1</em> and (if enabled) <em>sha256</em>.  <em>sha1</em> is the default.

+Specify the given object <em>&lt;format&gt;</em> (hash algorithm) for the repository.  The valid

+values are <code>sha1</code> and (if enabled) <code>sha256</code>.  <code>sha1</code> is the default.

 </p>

 <div class="paragraph"><p>Note: At present, there is no interoperability between SHA-256

 repositories and SHA-1 repositories.</p></div>

@@ -826,7 +826,7 @@ without data loss.</p></div>
 </dt>

 <dd>

 <p>

-Specify the given ref storage format for the repository. The valid values are:

+Specify the given ref storage <em>&lt;format&gt;</em> for the repository. The valid values are:

 </p>

 <div class="ulist"><ul>

 <li>

@@ -871,7 +871,7 @@ repository.
 </dt>

 <dd>

 <p>

-Use the specified name for the initial branch in the newly created

+Use <em>&lt;branch-name&gt;</em> for the initial branch in the newly created

 repository.  If not specified, fall back to the default name (currently

 <code>master</code>, but this is subject to change in the future; the name can be

 customized via the <code>init.defaultBranch</code> configuration variable).

@@ -884,18 +884,21 @@ customized via the <code>init.defaultBranch</code> configuration variable).
 <p>

 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

+repository.  When specified, the config variable <code>core.sharedRepository</code> is

 set so that files and directories under <code>$GIT_DIR</code> are created with the

 requested permissions.  When not specified, Git will use permissions reported

-by umask(2).

+by <code>umask(2)</code>.

 </p>

-<div class="paragraph"><p>The option can have the following values, defaulting to <em>group</em> if no value

+<div class="paragraph"><p>The option can have the following values, defaulting to <code>group</code> if no value

 is given:</p></div>

 <div class="openblock">

 <div class="content">

 <div class="dlist"><dl>

 <dt class="hdlist1">

-<em>umask</em> (or <em>false</em>)

+umask

+</dt>

+<dt class="hdlist1">

+false

 </dt>

 <dd>

 <p>

@@ -904,36 +907,45 @@ specified.
 </p>

 </dd>

 <dt class="hdlist1">

-<em>group</em> (or <em>true</em>)

+group

+</dt>

+<dt class="hdlist1">

+true

 </dt>

 <dd>

 <p>

 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 <em>0022</em>, using <em>group</em> will not remove read

-privileges from other (non-group) users). See <em>0xxx</em> for how to exactly specify

+permission bits (e.g. if umask is <code>0022</code>, using <code>group</code> will not remove read

+privileges from other (non-group) users). See <code>0xxx</code> for how to exactly specify

 the repository permissions.

 </p>

 </dd>

 <dt class="hdlist1">

-<em>all</em> (or <em>world</em> or <em>everybody</em>)

+all

+</dt>

+<dt class="hdlist1">

+world

+</dt>

+<dt class="hdlist1">

+everybody

 </dt>

 <dd>

 <p>

-Same as <em>group</em>, but make the repository readable by all users.

+Same as <code>group</code>, but make the repository readable by all users.

 </p>

 </dd>

 <dt class="hdlist1">

-<em>&lt;perm&gt;</em>

+&lt;perm&gt;

 </dt>

 <dd>

 <p>

 <em>&lt;perm&gt;</em> is a 3-digit octal number prefixed with &#8216;0` and each file

-will have mode <em>&lt;perm&gt;</em>. <em>&lt;perm&gt;</em> will override users&#8217; umask(2)

-value (and not only loosen permissions as <em>group</em> and <em>all</em>

-do). <em>0640</em> will create a repository which is group-readable, but

-not group-writable or accessible to others. <em>0660</em> will create a repo

+will have mode <em>&lt;perm&gt;</em>. <em>&lt;perm&gt;</em> will override users&#8217;<code>umask(2)</code>

+value (and not only loosen permissions as <code>group</code> and <code>all</code>

+do). <code>0640</code> will create a repository which is group-readable, but

+not group-writable or accessible to others. <code>0660</code> will create a repo

 that is readable and writable to the current user and group, but

 inaccessible to others (directories and executable files get their

 <code>x</code> bit from the <code>r</code> bit for corresponding classes of users).

@@ -946,7 +958,7 @@ inaccessible to others (directories and executable files get their
 <div class="paragraph"><p>By default, the configuration flag <code>receive.denyNonFastForwards</code> is enabled

 in shared repositories, so that you cannot force a non fast-forwarding push

 into it.</p></div>

-<div class="paragraph"><p>If you provide a <em>directory</em>, the command is run inside it. If this directory

+<div class="paragraph"><p>If you provide a <em>&lt;directory&gt;</em>, the command is run inside it. If this directory

 does not exist, it will be created.</p></div>

 </div>

 </div>

@@ -1003,7 +1015,7 @@ $ git commit    <b>&lt;3&gt;</b></code></pre>
 <div class="colist arabic"><ol>

 <li>

 <p>

-Create a /path/to/my/codebase/.git directory.

+Create a <code>/path/to/my/codebase/.git</code> directory.

 </p>

 </li>

 <li>

@@ -1033,8 +1045,7 @@ init.templateDir
 </dt>

 <dd>

 <p>

-        Specify the directory from which templates will be copied.

-        (See the "TEMPLATE DIRECTORY" section of <a href="git-init.html">git-init(1)</a>.)

+        Specify the directory from which templates will be copied. 

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1060,7 +1071,7 @@ init.defaultBranch
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2024-01-16 12:41:37 PST

+ 2024-03-21 16:28:38 PDT

 </div>

 </div>

 </body>