On 4/18/07, Robin H. Johnson <robbat2@xxxxxxxxxx> wrote:
As for a usage case:
- J.PEBKAC.User gets a a tree (from a tarball or GIT, we should gain the
same output)
- Copies some file outside of the tree (the user is NOT smart enough,
and resists all reasonable attempts at edumacation)
- Modifies said file outside of tree.
- Contacts maintainer with entire changed file.
- User vanishes off the internet.
That's a valid case, but as Linus hints, that's a snippet of perl/bash
away to find "closest matches". We could have a
git-findclosestmatch <head> path/to/scan/ randomfile.c
That would quickly return a few candidates together with the commit
they appear in.
cheers,
martin
-
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