Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Autogenerated HTML docs for v1.7.9-rc1

  • Loading branch information...
commit 864ba899feabe96d77ee90737327a288bfc0b24b 1 parent 4fd2442
@gitster authored
View
16 RelNotes/1.7.6.6.txt
@@ -0,0 +1,16 @@
+Git v1.7.6.6 Release Notes
+==========================
+
+Fixes since v1.7.6.5
+--------------------
+
+ * The code to look up attributes for paths reused entries from a wrong
+ directory when two paths in question are in adjacent directories and
+ the name of the one directory is a prefix of the other.
+
+ * When producing a "thin pack" (primarily used in bundles and smart
+ HTTP transfers) out of a fully packed repository, we unnecessarily
+ avoided sending recent objects as a delta against objects we know
+ the other side has.
+
+Also contains minor fixes and documentation updates.
View
16 RelNotes/1.7.7.6.txt
@@ -0,0 +1,16 @@
+Git v1.7.7.6 Release Notes
+==========================
+
+Fixes since v1.7.7.5
+--------------------
+
+ * The code to look up attributes for paths reused entries from a wrong
+ directory when two paths in question are in adjacent directories and
+ the name of the one directory is a prefix of the other.
+
+ * When producing a "thin pack" (primarily used in bundles and smart
+ HTTP transfers) out of a fully packed repository, we unnecessarily
+ avoided sending recent objects as a delta against objects we know
+ the other side has.
+
+Also contains minor fixes and documentation updates.
View
19 RelNotes/1.7.8.4.txt
@@ -0,0 +1,19 @@
+Git v1.7.8.4 Release Notes
+==========================
+
+Fixes since v1.7.8.3
+--------------------
+
+ * The code to look up attributes for paths reused entries from a wrong
+ directory when two paths in question are in adjacent directories and
+ the name of the one directory is a prefix of the other.
+
+ * When producing a "thin pack" (primarily used in bundles and smart
+ HTTP transfers) out of a fully packed repository, we unnecessarily
+ avoided sending recent objects as a delta against objects we know
+ the other side has.
+
+ * "git send-email" did not properly treat sendemail.multiedit as a
+ boolean (e.g. setting it to "false" did not turn it off).
+
+Also contains minor fixes and documentation updates.
View
6 RelNotes/1.7.9.txt
@@ -28,6 +28,10 @@ Updates since v1.7.8
building more generic "sequencer" on top of the implementation that
drives them.
+ * "git rev-parse FETCH_HEAD" after "git fetch" without specifying
+ what to fetch from the command line will now show the commit that
+ would be merged if the command were "git pull".
+
* "git add" learned to stream large files directly into a packfile
instead of writing them into individual loose object files.
@@ -108,7 +112,7 @@ details).
--
exec >/var/tmp/1
-O=v1.7.8.2-301-g48de656
+O=v1.7.9-rc0-44-g478c446
echo O=$(git describe master)
git log --first-parent --oneline --reverse ^$O master
echo
View
3  config.txt
@@ -1786,7 +1786,8 @@ rerere.enabled::
conflict hunks can be resolved automatically, should they be
encountered again. By default, linkgit:git-rerere[1] is
enabled if there is an `rr-cache` directory under the
- `$GIT_DIR`.
+ `$GIT_DIR`, e.g. if "rerere" was previously used in the
+ repository.
sendemail.identity::
A configuration identity. When given, causes values in the
View
3  git-config.html
@@ -4472,7 +4472,8 @@ <h3 id="_variables">Variables</h3><div style="clear:left"></div>
conflict hunks can be resolved automatically, should they be
encountered again. By default, <a href="git-rerere.html">git-rerere(1)</a> is
enabled if there is an <tt>rr-cache</tt> directory under the
- <tt>$GIT_DIR</tt>.
+ <tt>$GIT_DIR</tt>, e.g. if "rerere" was previously used in the
+ repository.
</p>
</dd>
<dt class="hdlist1">
View
34 git-mailinfo.html
@@ -604,14 +604,32 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- Usually the program <em>cleans up</em> the Subject: header line
- to extract the title line for the commit log message,
- among which (1) remove <em>Re:</em> or <em>re:</em>, (2) leading
- whitespaces, (3) <em>[</em> up to <em>]</em>, typically <em>[PATCH]</em>, and
- then prepends "[PATCH] ". This flag forbids this
- munging, and is most useful when used to read back
- <em>git format-patch -k</em> output.
+ Usually the program removes email cruft from the Subject:
+ header line to extract the title line for the commit log
+ message. This option prevents this munging, and is most
+ useful when used to read back <em>git format-patch -k</em> output.
</p>
+<div class="paragraph"><p>Specifically, the following are removed until none of them remain:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Leading and trailing whitespace.
+</p>
+</li>
+<li>
+<p>
+Leading <tt>Re:</tt>, <tt>re:</tt>, and <tt>:</tt>.
+</p>
+</li>
+<li>
+<p>
+Leading bracketed strings (between <tt>[</tt> and <tt>]</tt>, usually
+ <tt>[PATCH]</tt>).
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Finally, runs of whitespace are normalized to a single ASCII space
+character.</p></div>
</dd>
<dt class="hdlist1">
-b
@@ -708,7 +726,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 PDT
+Last updated 2012-01-13 09:41:44 PDT
</div>
</div>
</body>
View
25 git-mailinfo.txt
@@ -25,13 +25,24 @@ command directly. See linkgit:git-am[1] instead.
OPTIONS
-------
-k::
- Usually the program 'cleans up' the Subject: header line
- to extract the title line for the commit log message,
- among which (1) remove 'Re:' or 're:', (2) leading
- whitespaces, (3) '[' up to ']', typically '[PATCH]', and
- then prepends "[PATCH] ". This flag forbids this
- munging, and is most useful when used to read back
- 'git format-patch -k' output.
+ Usually the program removes email cruft from the Subject:
+ header line to extract the title line for the commit log
+ message. This option prevents this munging, and is most
+ useful when used to read back 'git format-patch -k' output.
++
+Specifically, the following are removed until none of them remain:
++
+--
+* Leading and trailing whitespace.
+
+* Leading `Re:`, `re:`, and `:`.
+
+* Leading bracketed strings (between `[` and `]`, usually
+ `[PATCH]`).
+--
++
+Finally, runs of whitespace are normalized to a single ASCII space
+character.
-b::
When -k is not in effect, all leading strings bracketed with '['
Please sign in to comment.
Something went wrong with that request. Please try again.