Ramkumar Ramachandra <artag...@gmail.com> writes:
> was checking it out: a 'git log <pathspec>', when referring to a file
> inside the subtree, doesn't work as expected: it only displays the
> HEAD commit.
This is somehow expected: the subtree merge changed the filename during
merge (it is subtree/file.txt after the merge, and just file.txt
before), so "git log" without --follow just considers the file appeared.
OTOH, I think this is a known limitation of "git log --follow" that it
does not follow renames done by subtree merges.
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