Patch series kept in a sibling repo: check the remote default branch, not the local checkout

When asked to explain a series of patch files kept in another repo, I listed the directory in the local checkout, which was on a stale feature branch, and missed the two newest patches, which existed only on origin/master. Before summarizing a patch series, run git fetch and git ls-tree --name-only origin/<default> <dir>, or loop over all remote branches, so you see every numbered patch. Also read the commit messages: each patch's real motivation (the bug or test seed that caused it) is usually only there, not in the diff comments.