Let's say I have a simple repo with three paths:
git init -q repo
for i in a b c
echo content >$i.t
git add $i.t
git commit -qm $i &&
git tag $i
If I ask for the top 2 commits, with the third as a boundary, I get the
$ git log --format='%m %s' --boundary a..c
If I limit the path to "b.t", I get:
$ git log --format='%m %s' --boundary a..c -- b.t
That makes sense to me. We omit "c" because it doesn't touch "b.t", and
obviously include "b", which does. We _do_ include the boundary commit,
even though it doesn't touch the path, which makes sense to me. It
remains a boundary whether it touched the path or not, and without it,
we get no boundary at all.
But now if I limit to "a.t", I get no output at all:
$ git log --format='%m %s' --boundary a..c -- a.t
whereas I would have expected "- a" to show the boundary.
Is this a bug, or are my expectations wrong?
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