to run after each revision is checked out to determine if it
is good or bad, to automate the bisection process.
+ - "git log" family learned a new traversal option --first-parent,
+ which does what the name suggests.
+
* Updated behaviour of existing commands.
- "git fsck" does not barf on corrupt loose objects.
+ - "git rm" does not remove newly added files without -f.
+
- "git archimport" allows remapping when coming up with git
branch names from arch names.
--
exec >/var/tmp/1
-O=v1.5.1-rc1-63-g12d6697
+O=v1.5.1-rc3-18-ge881192
echo O=`git describe master`
git shortlog --no-merges $O..master ^maint
Valid merge tools are:\r
kdiff3, tkdiff, meld, xxdiff, emerge, and vimdiff.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>If a merge resolution program is not specified, 'git mergetool'\r
+<p>If a merge resolution program is not specified, <em>git mergetool</em>\r
will use the configuration variable merge.tool. If the\r
-configuration variable merge.tool is not set, 'git mergetool'\r
-will pick a suitable default.</tt></pre>\r
-</div></div>\r
+configuration variable merge.tool is not set, <em>git mergetool</em>\r
+will pick a suitable default.</p>\r
</dd>\r
</dl>\r
</div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Mar-2007 10:43:14 UTC\r
+Last updated 30-Mar-2007 08:52:09 UTC\r
</div>\r
</div>\r
</body>\r
Use the merge resolution program specified by <tool>.
Valid merge tools are:
kdiff3, tkdiff, meld, xxdiff, emerge, and vimdiff.
-
- If a merge resolution program is not specified, 'git mergetool'
- will use the configuration variable merge.tool. If the
- configuration variable merge.tool is not set, 'git mergetool'
- will pick a suitable default.
++
+If a merge resolution program is not specified, 'git mergetool'
+will use the configuration variable merge.tool. If the
+configuration variable merge.tool is not set, 'git mergetool'
+will pick a suitable default.
Author
------
<p>Here are a handful examples:</p>\r
<div class="literalblock">\r
<div class="content">\r
-<pre><tt>D A B D\r
-D F A B C D F\r
-^A G B D\r
-^A F B C F\r
-G...I C D F G I\r
-^B G I C D F G I\r
-F^@ A B C\r
-F^! H D F H</tt></pre>\r
+<pre><tt>D G H D\r
+D F G H I J D F\r
+^G D H D\r
+^D B E I J F B\r
+B...C G H D E B C\r
+^D B C E I J F B C\r
+C^@ I J F\r
+F^! D G H D F</tt></pre>\r
</div></div>\r
</div>\r
<h2>Author</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 01-Mar-2007 01:24:43 UTC\r
+Last updated 30-Mar-2007 08:52:09 UTC\r
</div>\r
</div>\r
</body>\r
Here are a handful examples:
- D A B D
- D F A B C D F
- ^A G B D
- ^A F B C F
- G...I C D F G I
- ^B G I C D F G I
- F^@ A B C
- F^! H D F H
+ D G H D
+ D F G H I J D F
+ ^G D H D
+ ^D B E I J F B
+ B...C G H D E B C
+ ^D B C E I J F B C
+ C^@ I J F
+ F^! D G H D F
Author
------
repository, or incrementally import into an existing one.</p>\r
<p>SVN access is done by the SVN::Perl module.</p>\r
<p>git-svnimport assumes that SVN repositories are organized into one\r
-"trunk" directory where the main development happens, "branch/FOO"\r
+"trunk" directory where the main development happens, "branches/FOO"\r
directories for branches, and "/tags/FOO" directories for tags.\r
Other subdirectories are ignored.</p>\r
<p>git-svnimport creates a file ".git/svn2git", which is required for\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2007 07:43:49 UTC\r
+Last updated 30-Mar-2007 08:52:09 UTC\r
</div>\r
</div>\r
</body>\r
SVN access is done by the SVN::Perl module.
git-svnimport assumes that SVN repositories are organized into one
-"trunk" directory where the main development happens, "branch/FOO"
+"trunk" directory where the main development happens, "branches/FOO"
directories for branches, and "/tags/FOO" directories for tags.
Other subdirectories are ignored.
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Mar-2007 01:09:27 UTC\r
+Last updated 30-Mar-2007 08:52:09 UTC\r
</div>\r
</div>\r
</body>\r