Permalink
Browse files

Autogenerated HTML docs for v1.8.3-101-g727a4

  • Loading branch information...
1 parent b659547 commit c710296399a86586e3a5e24ea8519ea2442ab7cf @gitster committed May 29, 2013
View
@@ -0,0 +1,68 @@
+Git v1.8.4 Release Notes
+========================
+
+Updates since v1.8.3
+--------------------
+
+Foreign interface
+
+ * Remote transport helper has been updated to report errors and
+ maintain ref hierarchy used to keep track of its own state better.
+
+
+UI, Workflows & Features
+
+ * "check-ignore" (new feature since 1.8.2) has been updated to work
+ more like "check-attr" over bidi-pipes.
+
+ * We used the approxidate() parser for "--expire=<timestamp>" options
+ of various commands, but it is better to treat --expire=all and
+ --expire=now a bit more specially than using the current timestamp.
+ "git gc" and "git reflog" have been updated with a new parsing
+ function for expiry dates.
+
+
+Performance, Internal Implementation, etc.
+
+ * Object lookup logic, when the object hashtable starts to become
+ crowded, has been optimized.
+
+ * When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat
+ inconsistently between the test framework and t/Makefile, and logic
+ to summarize the results looked at a wrong place.
+
+ * Many warnings from sparse source checker in compat/ area has been
+ squelched.
+
+ * The code to reading and updating packed-refs file has been updated,
+ correcting corner case bugs.
+
+
+Also contains various documentation updates and code clean-ups.
+
+
+Fixes since v1.8.3
+------------------
+
+Unless otherwise noted, all the fixes since v1.8.3 in the maintenance
+track are contained in this release (see release notes to them for
+details).
+
+ * When $HOME is misconfigured to point at an unreadable directory, we
+ used to complain and die. Loosen the check.
+ (merge 4698c8f jn/config-ignore-inaccessible later to maint).
+
+ * "git subtree" (in contrib/) had one codepath with loose error
+ checks to lose data at the remote side.
+ (merge 3212d56 jk/subtree-do-not-push-if-split-fails later to maint).
+
+ * "git fetch" into a shallow repository from a repository that does
+ not know about the shallow boundary commits (e.g. a different fork
+ from the repository the current shallow repository was cloned from)
+ did not work correctly.
+ (merge 71d5f93 mh/fetch-into-shallow later to maint).
+
+ * "git checkout foo" DWIMs the intended "upstream" and turns it into
+ "git checkout -t -b foo remotes/origin/foo". This codepath has been
+ updated to correctly take existing remote definitions into account.
+ (merge 229177a jh/checkout-auto-tracking later to maint).
View
@@ -480,7 +480,7 @@ endif::git-format-patch[]
--ignore-submodules[=<when>]::
Ignore changes to submodules in the diff generation. <when> can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -854,6 +854,10 @@ <h2 id="_output">OUTPUT</h2>
</p>
</dd>
</dl></div>
+<div class="paragraph"><p>Buffering happens as documented under the <code>GIT_FLUSH</code> option in
+<a href="git.html">git(1)</a>. The caller is responsible for avoiding deadlocks
+caused by overfilling an input buffer or reading from an empty output
+buffer.</p></div>
</div>
</div>
<div class="sect1">
@@ -948,7 +952,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-05-29 16:56:14 PDT
</div>
</div>
</body>
View
@@ -56,6 +56,11 @@ being queried and <info> can be either:
'set';; when the attribute is defined as true.
<value>;; when a value has been assigned to the attribute.
+Buffering happens as documented under the `GIT_FLUSH` option in
+linkgit:git[1]. The caller is responsible for avoiding deadlocks
+caused by overfilling an input buffer or reading from an empty output
+buffer.
+
EXAMPLES
--------
View
@@ -802,6 +802,17 @@ <h2 id="_options">OPTIONS</h2>
with a NUL character instead of a linefeed character.
</p>
</dd>
+<dt class="hdlist1">
+-n, --non-matching
+</dt>
+<dd>
+<p>
+ Show given paths which don&#8217;t match any pattern. This only
+ makes sense when <code>--verbose</code> is enabled, otherwise it would
+ not be possible to distinguish between paths which match a
+ pattern and those which don&#8217;t.
+</p>
+</dd>
</dl></div>
</div>
</div>
@@ -825,6 +836,19 @@ <h2 id="_output">OUTPUT</h2>
null character; if <code>--verbose</code> is also specified then null characters
are also used instead of colons and hard tabs:</p></div>
<div class="paragraph"><p>&lt;source&gt; &lt;NULL&gt; &lt;linenum&gt; &lt;NULL&gt; &lt;pattern&gt; &lt;NULL&gt; &lt;pathname&gt; &lt;NULL&gt;</p></div>
+<div class="paragraph"><p>If <code>-n</code> or <code>--non-matching</code> are specified, non-matching pathnames will
+also be output, in which case all fields in each output record except
+for &lt;pathname&gt; will be empty. This can be useful when running
+non-interactively, so that files can be incrementally streamed to
+STDIN of a long-running check-ignore process, and for each of these
+files, STDOUT will indicate whether that file matched a pattern or
+not. (Without this option, it would be impossible to tell whether the
+absence of output for a given file meant that it didn&#8217;t match any
+pattern, or that the output hadn&#8217;t been generated yet.)</p></div>
+<div class="paragraph"><p>Buffering happens as documented under the <code>GIT_FLUSH</code> option in
+<a href="git.html">git(1)</a>. The caller is responsible for avoiding deadlocks
+caused by overfilling an input buffer or reading from an empty output
+buffer.</p></div>
</div>
</div>
<div class="sect1">
@@ -876,7 +900,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-01-25 13:32:06 PST
+Last updated 2013-05-29 16:56:14 PDT
</div>
</div>
</body>
View
@@ -39,6 +39,12 @@ OPTIONS
below). If `--stdin` is also given, input paths are separated
with a NUL character instead of a linefeed character.
+-n, --non-matching::
+ Show given paths which don't match any pattern. This only
+ makes sense when `--verbose` is enabled, otherwise it would
+ not be possible to distinguish between paths which match a
+ pattern and those which don't.
+
OUTPUT
------
@@ -65,6 +71,20 @@ are also used instead of colons and hard tabs:
<source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>
+If `-n` or `--non-matching` are specified, non-matching pathnames will
+also be output, in which case all fields in each output record except
+for <pathname> will be empty. This can be useful when running
+non-interactively, so that files can be incrementally streamed to
+STDIN of a long-running check-ignore process, and for each of these
+files, STDOUT will indicate whether that file matched a pattern or
+not. (Without this option, it would be impossible to tell whether the
+absence of output for a given file meant that it didn't match any
+pattern, or that the output hadn't been generated yet.)
+
+Buffering happens as documented under the `GIT_FLUSH` option in
+linkgit:git[1]. The caller is responsible for avoiding deadlocks
+caused by overfilling an input buffer or reading from an empty output
+buffer.
EXIT STATUS
-----------
View
@@ -927,9 +927,9 @@ <h2 id="_options">OPTIONS</h2>
"--track" in <a href="git-branch.html">git-branch(1)</a> for details.
</p>
<div class="paragraph"><p>If no <em>-b</em> option is given, the name of the new branch will be
-derived from the remote-tracking branch. If "remotes/" or "refs/remotes/"
-is prefixed it is stripped away, and then the part up to the
-next slash (which would be the nickname of the remote) is removed.
+derived from the remote-tracking branch, by looking at the local part of
+the refspec configured for the corresponding remote, and then stripping
+the initial part up to the "*".
This would tell us to use "hack" as the local branch when branching
off of "origin/hack" (or "remotes/origin/hack", or even
"refs/remotes/origin/hack"). If the given name has no slash, or the above
@@ -1360,7 +1360,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-04-22 12:12:24 PDT
+Last updated 2013-05-29 16:56:14 PDT
</div>
</div>
</body>
View
@@ -131,9 +131,9 @@ entries; instead, unmerged entries are ignored.
"--track" in linkgit:git-branch[1] for details.
+
If no '-b' option is given, the name of the new branch will be
-derived from the remote-tracking branch. If "remotes/" or "refs/remotes/"
-is prefixed it is stripped away, and then the part up to the
-next slash (which would be the nickname of the remote) is removed.
+derived from the remote-tracking branch, by looking at the local part of
+the refspec configured for the corresponding remote, and then stripping
+the initial part up to the "*".
This would tell us to use "hack" as the local branch when branching
off of "origin/hack" (or "remotes/origin/hack", or even
"refs/remotes/origin/hack"). If the given name has no slash, or the above
View
@@ -1548,7 +1548,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -1549,7 +1549,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -1550,7 +1550,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -1647,7 +1647,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -1310,7 +1310,7 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -815,8 +815,9 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Prune loose objects older than date (default is 2 weeks ago,
- overridable by the config variable <code>gc.pruneExpire</code>). This
- option is on by default.
+ overridable by the config variable <code>gc.pruneExpire</code>).
+ --prune=all prunes loose objects regardless of their age.
+ --prune is on by default.
</p>
</dd>
<dt class="hdlist1">
@@ -924,7 +925,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-05-02 15:00:44 PDT
+Last updated 2013-05-29 16:56:14 PDT
</div>
</div>
</body>
View
@@ -62,8 +62,9 @@ automatic consolidation of packs.
--prune=<date>::
Prune loose objects older than date (default is 2 weeks ago,
- overridable by the config variable `gc.pruneExpire`). This
- option is on by default.
+ overridable by the config variable `gc.pruneExpire`).
+ --prune=all prunes loose objects regardless of their age.
+ --prune is on by default.
--no-prune::
Do not prune any loose objects.
View
@@ -3314,7 +3314,7 @@ <h2 id="_common_diff_options">Common diff options</h2>
<dd>
<p>
Ignore changes to submodules in the diff generation. &lt;when&gt; can be
- either "none", "untracked", "dirty" or "all", which is the default
+ either "none", "untracked", "dirty" or "all", which is the default.
Using "none" will consider the submodule modified when it either contains
untracked or modified files or its HEAD differs from the commit recorded
in the superproject and can be used to override any settings of the
View
@@ -813,7 +813,9 @@ <h2 id="_options">OPTIONS</h2>
<p>
Entries older than this time are pruned. Without the
option it is taken from configuration <code>gc.reflogExpire</code>,
- which in turn defaults to 90 days.
+ which in turn defaults to 90 days. --expire=all prunes
+ entries regardless of their age; --expire=never turns off
+ pruning of reachable entries (but see --expire-unreachable).
</p>
</dd>
<dt class="hdlist1">
@@ -825,7 +827,10 @@ <h2 id="_options">OPTIONS</h2>
the current tip of the branch are pruned. Without the
option it is taken from configuration
<code>gc.reflogExpireUnreachable</code>, which in turn defaults to
- 30 days.
+ 30 days. --expire-unreachable=all prunes unreachable
+ entries regardless of their age; --expire-unreachable=never
+ turns off early pruning of unreachable entries (but see
+ --expire).
</p>
</dd>
<dt class="hdlist1">
@@ -876,7 +881,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-05-29 16:56:14 PDT
</div>
</div>
</body>
View
@@ -67,14 +67,19 @@ them.
--expire=<time>::
Entries older than this time are pruned. Without the
option it is taken from configuration `gc.reflogExpire`,
- which in turn defaults to 90 days.
+ which in turn defaults to 90 days. --expire=all prunes
+ entries regardless of their age; --expire=never turns off
+ pruning of reachable entries (but see --expire-unreachable).
--expire-unreachable=<time>::
Entries older than this time and not reachable from
the current tip of the branch are pruned. Without the
option it is taken from configuration
`gc.reflogExpireUnreachable`, which in turn defaults to
- 30 days.
+ 30 days. --expire-unreachable=all prunes unreachable
+ entries regardless of their age; --expire-unreachable=never
+ turns off early pruning of unreachable entries (but see
+ --expire).
--all::
Instead of listing <refs> explicitly, prune all refs.
View
@@ -2594,8 +2594,9 @@ <h3 id="_other">other</h3>
<p>
If this environment variable is set to "1", then commands such
as <em>git blame</em> (in incremental mode), <em>git rev-list</em>, <em>git log</em>,
- and <em>git whatchanged</em> will force a flush of the output stream
- after each commit-oriented record have been flushed. If this
+ <em>git check-attr</em>, <em>git check-ignore</em>, and <em>git whatchanged</em> will
+ force a flush of the output stream after each record have been
+ flushed. If this
variable is set to "0", the output of these commands will be done
using completely buffered I/O. If this environment variable is
not set, Git will choose buffered or record-oriented flushing
@@ -2743,7 +2744,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-09 14:34:12 PDT
+Last updated 2013-05-29 16:56:14 PDT
</div>
</div>
</body>
Oops, something went wrong.

0 comments on commit c710296

Please sign in to comment.