Thomas Rast <trast@xxxxxxxxxxxxxxx> writes:
> 'git log -- <path>' does not "show commits that affect the specified
> paths" in a literal sense unless --full-history is given (for example,
> a file that only existed on a side branch will turn up no commits at
> all!).
>
> Point the user to the "History Simplification" section to avoid
> surprises.
Hmm, or perhaps replace it with a brief explanation instead of redirecting
the readers to a separate section without telling them anything here?
Show only commits that are enough to explain how the files that match
the specified paths came to be.
(this is my attempt to paraphrase $gmane/90659)
> [\--] <path>...::
> + Show only commits that affect any of the specified paths.
> + See "History Simplification" below for a precise definition of
> + the filtering applied.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html