On 06/13/2014 05:52 PM, Jakub Narębski wrote:
> I don't know if it has been fixed, but there is a difference
> between "git diff A...B" when A and B have one merge base, and
> "git diff A...B" when there are more than one merge base.
> When there is one merge base, "git diff A...B" returns simple
> unified diff equivalent to "git diff $(git merge-base A B) B".
> It is unsymmetric.
> But where there are more than one merge base, by design or by
> accident for "git diff A...B" git 1.9.2 / 1.7.4 returns
> git diff --cc $(git merge-base --all A B) A B
> which is *symmetric*, and is combined not unified diff.
Thanks for the information. This doesn't seem to be the case in git
2.0.0. For example, commit 8c0db2f519 in the git project is a merge
with two merge bases:
$ git --version
git version 2.0.0
$ git merge-base --all $c^1 $c^2
$ git diff $c^1...$c^2 | head -20
diff --git a/Documentation/git-rev-parse.txt
index d638bfc..29b5789 100644
@@ -77,6 +77,14 @@ OPTIONS
path of the top-level directory relative to the current
directory (typically a sequence of "../", or an empty string).
+ Show `$GIT_DIR` if defined else show the path to the .git directory.
+ Instead of outputting the full SHA1 values of object names try to
+ abbriviate them to a shorter unique name. When no length is specified
+ 7 is used. The minimum length is 4.
Parses the date string, and outputs corresponding
--max-age= parameter for git-rev-list command.
diff --git a/git-archimport.perl b/git-archimport.perl
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html