Permalink
Browse files

Autogenerated HTML docs for v1.8.4-rc0

  • Loading branch information...
1 parent 58f587a commit d7fccbf9c67ab9111bc853a5fc90aa87d2d3f9c0 @gitster committed Jul 25, 2013
View
@@ -14,7 +14,7 @@ Fixes since v1.7.10
not exclude them and tried to apply funny patches only to fail.
* "git blame" started missing quite a few changes from the origin
- since we stopped using the diff minimalization by default in v1.7.2
+ since we stopped using the diff minimization by default in v1.7.2
era.
* When PATH contains an unreadable directory, alias expansion code
View
@@ -5,7 +5,7 @@ Fixes since v1.7.5.3
--------------------
* The single-key mode of "git add -p" was easily fooled into thinking
- that it was told to add everthing ('a') when up-arrow was pressed by
+ that it was told to add everything ('a') when up-arrow was pressed by
mistake.
* Setting a git command that uses custom configuration via "-c var=val"
View
@@ -12,11 +12,11 @@ Fixes since v1.7.8.1
* The configuration file parser used for sizes (e.g. bigFileThreshold)
did not correctly interpret 'g' suffix.
- * The replacement implemention for snprintf used on platforms with
+ * The replacement implementation for snprintf used on platforms with
native snprintf that is broken did not use va_copy correctly.
* LF-to-CRLF streaming filter replaced all LF with CRLF, which might
- be techinically correct but not friendly to people who are trying
+ be technically correct but not friendly to people who are trying
to recover from earlier mistakes of using CRLF in the repository
data in the first place. It now refrains from doing so for LF that
follows a CR.
View
@@ -9,7 +9,7 @@ Updates since v1.7.7
* Updates to bash completion scripts.
* The build procedure has been taught to take advantage of computed
- dependency automatically when the complier supports it.
+ dependency automatically when the compiler supports it.
* The date parser now accepts timezone designators that lack minutes
part and also has a colon between "hh:mm".
@@ -31,7 +31,7 @@ Updates since v1.7.7
* Variants of "git cherry-pick" and "git revert" that take multiple
commits learned to "--continue" and "--abort".
- * "git daemon" gives more human readble error messages to clients
+ * "git daemon" gives more human readable error messages to clients
using ERR packets when appropriate.
* Errors at the network layer is logged by "git daemon".
View
@@ -49,7 +49,7 @@ Fixes since v1.8.2
common prefix and suffix between the two filenames overlapped.
* "git submodule update", when recursed into sub-submodules, did not
- acccumulate the prefix paths.
+ accumulate the prefix paths.
* "git am $maildir/" applied messages in an unexpected order; sort
filenames read from the maildir/ in a way that is more likely to
View
@@ -58,4 +58,4 @@ Fixes since v1.8.2.1
conflicts have been applied.
* "git bundle" did not like a bundle created using a commit without
- any message as its one of the prerequistes.
+ any message as its one of the prerequisites.
View
@@ -48,6 +48,8 @@ Updates since v1.8.3
Foreign interfaces, subsystems and ports.
+ * Cygwin port has been updated for more recent Cygwin 1.7.
+
* "git rebase -i" now honors --strategy and -X options.
* Git-gui has been updated to its 0.18.0 version.
@@ -83,6 +85,12 @@ Foreign interfaces, subsystems and ports.
UI, Workflows & Features
+ * Sample "post-receive-email" hook script got an enhanced replacement
+ "multimail" (in contrib/).
+
+ * Also in contrib/ is a new "contacts" script that runs "git blame"
+ to find out the people who may be interested in a set of changes.
+
* "git clean" command learned an interactive mode.
* The "--head" option to "git show-ref" was only to add "HEAD" to the
@@ -182,7 +190,7 @@ UI, Workflows & Features
directly uses the 40-hex string as an object name, even if a ref
"refs/<some hierarchy>/<name>" exists. This disambiguation order
is unlikely to change, but we should warn about the ambiguity just
- like we warn when more than one refs/ hierachies share the same
+ like we warn when more than one refs/ hierarchies share the same
name.
* "git rebase" learned "--[no-]autostash" option to save local
View
@@ -1903,7 +1903,7 @@ <h2 id="_conclusion">Conclusion</h2>
</div>
</div>
<div class="sect1">
-<h2 id="_acknowledgements">Acknowledgements</h2>
+<h2 id="_acknowledgments">Acknowledgments</h2>
<div class="sectionbody">
<div class="paragraph"><p>Many thanks to Junio Hamano for his help in reviewing this paper, for
reviewing the patches I sent to the Git mailing list, for discussing
@@ -1979,7 +1979,7 @@ <h2 id="_references">References</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-02-05 21:07:26 PST
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
View
@@ -1320,7 +1320,7 @@ So git bisect is unconditional goodness - and feel free to quote that
;-)
_____________
-Acknowledgements
+Acknowledgments
----------------
Many thanks to Junio Hamano for his help in reviewing this paper, for
View
@@ -1468,7 +1468,7 @@ <h3 id="_history_simplification">History Simplification</h3>
</li>
<li>
<p>
-<code>X</code> is an indpendent root commit that added a new file <code>side</code>, and <code>Y</code>
+<code>X</code> is an independent root commit that added a new file <code>side</code>, and <code>Y</code>
modified it. <code>Y</code> is TREESAME to <code>X</code>. Its merge <code>Q</code> added <code>side</code> to <code>P</code>, and
<code>Q</code> is TREESAME to <code>P</code>, but not to <code>Y</code>.
</p>
View
@@ -771,8 +771,8 @@ <h2 id="_description">DESCRIPTION</h2>
<div class="paragraph"><p>Subsequent updates to branches always create new files under
<code>$GIT_DIR/refs</code> directory hierarchy.</p></div>
<div class="paragraph"><p>A recommended practice to deal with a repository with too many
-refs is to pack its refs with <code>--all --prune</code> once, and
-occasionally run <code>git pack-refs --prune</code>. Tags are by
+refs is to pack its refs with <code>--all</code> once, and
+occasionally run <code>git pack-refs</code>. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial <code>pack-refs --all</code>, but
only the currently active branch heads will become unpacked,
@@ -827,7 +827,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-08-22 12:54:47 PDT
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
View
@@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
`$GIT_DIR/refs` directory hierarchy.
A recommended practice to deal with a repository with too many
-refs is to pack its refs with `--all --prune` once, and
-occasionally run `git pack-refs --prune`. Tags are by
+refs is to pack its refs with `--all` once, and
+occasionally run `git pack-refs`. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked,
View
@@ -838,7 +838,7 @@ <h2 id="_example">EXAMPLE</h2>
<code>.git/objects/info/alternates</code>:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code>$ git prune $(cd ../another &amp;&amp; $(git rev-parse --all))</code></pre>
+<pre><code>$ git prune $(cd ../another &amp;&amp; git rev-parse --all)</code></pre>
</div></div>
</div>
</div>
@@ -870,7 +870,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2011-11-15 13:45:02 PST
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
View
@@ -59,7 +59,7 @@ borrows from your repository via its
`.git/objects/info/alternates`:
------------
-$ git prune $(cd ../another && $(git rev-parse --all))
+$ git prune $(cd ../another && git rev-parse --all)
------------
Notes
View
@@ -1415,7 +1415,7 @@ <h3 id="_history_simplification">History Simplification</h3>
</li>
<li>
<p>
-<code>X</code> is an indpendent root commit that added a new file <code>side</code>, and <code>Y</code>
+<code>X</code> is an independent root commit that added a new file <code>side</code>, and <code>Y</code>
modified it. <code>Y</code> is TREESAME to <code>X</code>. Its merge <code>Q</code> added <code>side</code> to <code>P</code>, and
<code>Q</code> is TREESAME to <code>P</code>, but not to <code>Y</code>.
</p>
View
@@ -83,7 +83,7 @@ eval "set -- $(git rev-parse --sq --prefix "$prefix" "$@")"
+
If you want to make sure that the output actually names an object in
your object database and/or can be used as a specific type of object
-you require, you can add "^{type}" peeling operator to the parmeter.
+you require, you can add "^{type}" peeling operator to the parameter.
For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
names an existing object that is a commit-ish (i.e. a commit, or an
annotated tag that points at a commit). To make sure that `$VAR`
View
@@ -1432,7 +1432,7 @@ <h3 id="_single_url_for_gitweb_and_for_fetching">Single URL for gitweb and for f
</div></div>
<div class="paragraph"><p>The above configuration expects your public repositories to live under
<em>/pub/git</em> and will serve them as <code>http://git.domain.org/dir-under-pub-git</code>,
-both as cloneable Git URL and as browseable gitweb interface. If you then
+both as clonable Git URL and as browseable gitweb interface. If you then
start your <a href="git-daemon.html">git-daemon(1)</a> with <code>--base-path=/pub/git --export-all</code>
then you can even use the <code>git://</code> URL with exactly the same path.</p></div>
<div class="paragraph"><p>Setting the environment variable <code>GITWEB_CONFIG</code> will tell gitweb to use the
@@ -1639,7 +1639,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-02-05 21:07:26 PST
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
View
@@ -504,7 +504,7 @@ repositories, you can configure Apache like this:
The above configuration expects your public repositories to live under
'/pub/git' and will serve them as `http://git.domain.org/dir-under-pub-git`,
-both as cloneable Git URL and as browseable gitweb interface. If you then
+both as clonable Git URL and as browseable gitweb interface. If you then
start your linkgit:git-daemon[1] with `--base-path=/pub/git --export-all`
then you can even use the `git://` URL with exactly the same path.
@@ -737,7 +737,7 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph"><p>One of the changes I pulled into the <em>master</em> branch turns out to
-break building Git with GCC 2.95. While they were well intentioned
+break building Git with GCC 2.95. While they were well-intentioned
portability fixes, keeping things working with gcc-2.95 was also
important. Here is what I did to revert the change in the <em>master</em>
branch and to adjust the <em>pu</em> branch, using core Git tools and
@@ -903,7 +903,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-24 12:39:03 PDT
+Last updated 2013-07-24 20:24:00 PDT
</div>
</div>
</body>
@@ -12,7 +12,7 @@ How to revert an existing commit
================================
One of the changes I pulled into the 'master' branch turns out to
-break building Git with GCC 2.95. While they were well intentioned
+break building Git with GCC 2.95. While they were well-intentioned
portability fixes, keeping things working with gcc-2.95 was also
important. Here is what I did to revert the change in the 'master'
branch and to adjust the 'pu' branch, using core Git tools and
View
@@ -369,7 +369,7 @@ each merge. The commits are:
* `E` changes `quux` to "xyzzy", and its merge `P` combines the
strings to "quux xyzzy". `P` is TREESAME to `O`, but not to `E`.
-* `X` is an indpendent root commit that added a new file `side`, and `Y`
+* `X` is an independent root commit that added a new file `side`, and `Y`
modified it. `Y` is TREESAME to `X`. Its merge `Q` added `side` to `P`, and
`Q` is TREESAME to `P`, but not to `Y`.
@@ -1042,7 +1042,7 @@ <h3 id="_resolve_undo">Resolve undo</h3>
<div class="content">
<pre><code>A conflict is represented in the index as a set of higher stage entries.
When a conflict is resolved (e.g. with "git add path"), these higher
-stage entries will be removed and a stage-0 entry with proper resoluton
+stage entries will be removed and a stage-0 entry with proper resolution
is added.</code></pre>
</div></div>
<div class="literalblock">
@@ -1089,7 +1089,7 @@ <h3 id="_resolve_undo">Resolve undo</h3>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-03-19 16:06:22 PDT
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
@@ -175,7 +175,7 @@ Git index format
A conflict is represented in the index as a set of higher stage entries.
When a conflict is resolved (e.g. with "git add path"), these higher
- stage entries will be removed and a stage-0 entry with proper resoluton
+ stage entries will be removed and a stage-0 entry with proper resolution
is added.
When these higher stage entries are removed, they are saved in the
View
@@ -776,7 +776,7 @@ <h2 id="_background">Background</h2>
on-disk timestamps, resulting in meaningless changes when an
inode is evicted from the inode cache. See commit 8ce13b0
of git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
-([PATCH] Sync in core time granuality with filesystems,
+([PATCH] Sync in core time granularity with filesystems,
2005-01-04).</p></div>
</div>
</div>
@@ -944,7 +944,7 @@ <h2 id="_avoiding_runtime_penalty">Avoiding runtime penalty</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-07-01 14:29:27 PDT
+Last updated 2013-07-24 20:23:45 PDT
</div>
</div>
</body>
View
@@ -46,7 +46,7 @@ because in-core timestamps can have finer granularity than
on-disk timestamps, resulting in meaningless changes when an
inode is evicted from the inode cache. See commit 8ce13b0
of git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
-([PATCH] Sync in core time granuality with filesystems,
+([PATCH] Sync in core time granularity with filesystems,
2005-01-04).
Racy Git

0 comments on commit d7fccbf

Please sign in to comment.