Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Autogenerated HTML docs for v1.8.1.2-459-gbcd45b

  • Loading branch information...
commit 0d1122eea27fe3cbafc19429c3f55048d5204092 1 parent 4cfed0c
Junio C Hamano authored
42 RelNotes/1.8.2.txt
View
@@ -50,6 +50,14 @@ UI, Workflows & Features
E.g. "foo/**/bar" matches "bar" in "foo" itself or in a
subdirectory of "foo".
+ * When giving arguments without "--" disambiguation, object names
+ that come earlier on the command line must not be interpretable as
+ pathspecs and pathspecs that come later on the command line must
+ not be interpretable as object names. This disambiguation rule has
+ been tweaked so that ":/" (no other string before or after) is
+ always interpreted as a pathspec; "git cmd -- :/" is no longer
+ needed, you can just say "git cmd :/".
+
* "git blame" (and "git diff") learned the "--no-follow" option.
* "git check-ignore" command to help debugging .gitignore files has
@@ -112,7 +120,8 @@ Foreign Interface
* A new remote helper to interact with bzr has been added to contrib/.
- * "git p4" got various bugfixes around its branch handling.
+ * "git p4" got various bugfixes around its branch handling. It is
+ also made usable with Python 2.4/2.5.
* The remote helper to interact with Hg in contrib/ has seen a few
fixes.
@@ -126,6 +135,11 @@ Performance, Internal Implementation, etc.
* Matching paths with common forms of pathspecs that contain wildcard
characters has been optimized further.
+ * We stopped paying attention to $GIT_CONFIG environment that points
+ at a single configuration file from any command other than "git config"
+ quite a while ago, but "git clone" internally set, exported, and
+ then unexported the variable during its operation unnecessarily.
+
* "git reset" internals has been reworked and should be faster in
general. We tried to be careful not to break any behaviour but
there could be corner cases, especially when running the command
@@ -153,6 +167,13 @@ Performance, Internal Implementation, etc.
USE_WILDMATCH, using the resulting Git daily and reporting when you
find breakages, you can help us get closer to that goal.
+ * Some reimplementations of Git do not write all the stat info back
+ to the index due to their implementation limitations (e.g. jgit).
+ A configuration option can tell Git to ignore changes to most of
+ the stat fields and only pay attention to mtime and size, which
+ these implementations can reliably update. This can be used to
+ avoid excessive revalidation of contents.
+
Also contains minor documentation updates and code clean-ups.
@@ -186,6 +207,11 @@ details).
* After failing to create a temporary file using mkstemp(), failing
pathname was not reported correctly on some platforms.
+ * We used to stuff "user@" and then append what we read from
+ /etc/mailname to come up with a default e-mail ident, but a bug
+ lost the "user@" part.
+ (merge dc342a2 jn/do-not-drop-username-when-reading-from-etc-mailname later to maint).
+
* The attribute mechanism didn't allow limiting attributes to be
applied to only a single directory itself with "path/" like the
exclude mechanism does. The initial implementation of this that
@@ -206,6 +232,10 @@ details).
* "git archive" did not record uncompressed size in the header when
streaming a zip archive, which confused some implementations of unzip.
+ * Attempt to "branch --edit-description" an existing branch, while
+ being on a detached HEAD, errored out.
+ (merge 75135b2 nd/edit-branch-desc-while-detached later to maint).
+
* "git clean" showed what it was going to do, but sometimes end up
finding that it was not allowed to do so, which resulted in a
confusing output (e.g. after saying that it will remove an
@@ -218,6 +248,12 @@ details).
failed to remove the real location of the $GIT_DIR it created.
This was most visible when interrupting a submodule update.
+ * "git fetch --depth" was broken in at least three ways. The
+ resulting history was deeper than specified by one commit, it was
+ unclear how to wipe the shallowness of the repository with the
+ command, and documentation was misleading.
+ (merge cfb70e1 nd/fetch-depth-is-broken later to maint).
+
* The way "git svn" asked for password using SSH_ASKPASS and
GIT_ASKPASS was not in line with the rest of the system.
@@ -306,3 +342,7 @@ details).
need to be in the cvsadmin group on NetBSD 6.0).
* t9020 and t9810 had a few non-portable shell script construct.
+
+ * Scripts to test bash completion was inherently flaky as it was
+ affected by whatever random things the user may have on $PATH.
+ (merge 5047822 jc/do-not-let-random-file-interfere-with-completion-tests later to maint).
6 fetch-options.txt
View
@@ -8,11 +8,15 @@
option old data in `.git/FETCH_HEAD` will be overwritten.
--depth=<depth>::
- Deepen the history of a 'shallow' repository created by
+ Deepen or shorten the history of a 'shallow' repository created by
`git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
to the specified number of commits from the tip of each remote
branch history. Tags for the deepened commits are not fetched.
+--unshallow::
+ Convert a shallow repository to a complete one, removing all
+ the limitations imposed by shallow repositories.
+
ifndef::git-pull[]
--dry-run::
Show what would be done, without making any changes.
7 git-cvsimport.html
View
@@ -758,6 +758,11 @@ <h2 id="_synopsis">SYNOPSIS</h2>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
+<div class="paragraph"><p><strong>WARNING:</strong> <code>git cvsimport</code> uses cvsps version 2, which is considered
+deprecated; it does not work with cvsps version 3 and later. If you are
+performing a one-shot import of a CVS repository consider using
+<a href="http://cvs2svn.tigris.org/cvs2git.html">cvs2git</a> or
+<a href="https://github.com/BartMassey/parsecvs">parsecvs</a>.</p></div>
<div class="paragraph"><p>Imports a CVS repository into git. It will either create a new
repository, or incrementally import into an existing one.</p></div>
<div class="paragraph"><p>Splitting the CVS log into patch sets is done by <em>cvsps</em>.
@@ -1098,7 +1103,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-01-09 12:49:56 PST
+Last updated 2013-02-01 13:36:31 PST
</div>
</div>
</body>
6 git-cvsimport.txt
View
@@ -18,6 +18,12 @@ SYNOPSIS
DESCRIPTION
-----------
+*WARNING:* `git cvsimport` uses cvsps version 2, which is considered
+deprecated; it does not work with cvsps version 3 and later. If you are
+performing a one-shot import of a CVS repository consider using
+link:http://cvs2svn.tigris.org/cvs2git.html[cvs2git] or
+link:https://github.com/BartMassey/parsecvs[parsecvs].
+
Imports a CVS repository into git. It will either create a new
repository, or incrementally import into an existing one.
4 git-fetch-pack.html
View
@@ -872,6 +872,8 @@ <h2 id="_options">OPTIONS</h2>
<dd>
<p>
Limit fetching to ancestor-chains not longer than n.
+ <em>git-upload-pack</em> treats the special depth 2147483647 as
+ infinite even if there is an ancestor-chain that long.
</p>
</dd>
<dt class="hdlist1">
@@ -931,7 +933,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-11-20 13:06:02 PST
+Last updated 2013-02-01 13:36:31 PST
</div>
</div>
</body>
2  git-fetch-pack.txt
View
@@ -84,6 +84,8 @@ be in a separate packet, and the list must end with a flush packet.
--depth=<n>::
Limit fetching to ancestor-chains not longer than n.
+ 'git-upload-pack' treats the special depth 2147483647 as
+ infinite even if there is an ancestor-chain that long.
--no-progress::
Do not show the progress.
11 git-fetch.html
View
@@ -805,13 +805,22 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- Deepen the history of a <em>shallow</em> repository created by
+ Deepen or shorten the history of a <em>shallow</em> repository created by
<code>git clone</code> with <code>--depth=&lt;depth&gt;</code> option (see <a href="git-clone.html">git-clone(1)</a>)
to the specified number of commits from the tip of each remote
branch history. Tags for the deepened commits are not fetched.
</p>
</dd>
<dt class="hdlist1">
+--unshallow
+</dt>
+<dd>
+<p>
+ Convert a shallow repository to a complete one, removing all
+ the limitations imposed by shallow repositories.
+</p>
+</dd>
+<dt class="hdlist1">
--dry-run
</dt>
<dd>
11 git-pull.html
View
@@ -1112,13 +1112,22 @@ <h3 id="_options_related_to_fetching">Options related to fetching</h3>
</dt>
<dd>
<p>
- Deepen the history of a <em>shallow</em> repository created by
+ Deepen or shorten the history of a <em>shallow</em> repository created by
<code>git clone</code> with <code>--depth=&lt;depth&gt;</code> option (see <a href="git-clone.html">git-clone(1)</a>)
to the specified number of commits from the tip of each remote
branch history. Tags for the deepened commits are not fetched.
</p>
</dd>
<dt class="hdlist1">
+--unshallow
+</dt>
+<dd>
+<p>
+ Convert a shallow repository to a complete one, removing all
+ the limitations imposed by shallow repositories.
+</p>
+</dd>
+<dt class="hdlist1">
-f
</dt>
<dt class="hdlist1">
4 technical/shallow.html
View
@@ -799,13 +799,15 @@
<div class="paragraph"><p>You can deepen a shallow repository with "git-fetch --depth 20
repo branch", which will fetch branch from repo, but stop at depth
20, updating $GIT_DIR/shallow.</p></div>
+<div class="paragraph"><p>The special depth 2147483647 (or 0x7fffffff, the largest positive
+number a signed 32-bit integer can contain) means infinite depth.</p></div>
</div>
</div>
</div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2012-11-20 13:06:02 PST
+Last updated 2013-02-01 13:36:31 PST
</div>
</div>
</body>
3  technical/shallow.txt
View
@@ -53,3 +53,6 @@ It also writes an appropriate $GIT_DIR/shallow.
You can deepen a shallow repository with "git-fetch --depth 20
repo branch", which will fetch branch from repo, but stop at depth
20, updating $GIT_DIR/shallow.
+
+The special depth 2147483647 (or 0x7fffffff, the largest positive
+number a signed 32-bit integer can contain) means infinite depth.
Please sign in to comment.
Something went wrong with that request. Please try again.