Re: [PATCH 2/2] Add keyword unexpansion support to convert.c

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Apr 18, 2007, 02:50 UTC
Message-ID: <46a038f90704171950g4b408fedm1028e7f934a9b53c@mail.gmail.com>
In-Reply-To: <20070417235649.GE31488@curie-int.orbis-terrarum.net>

On 4/18/07, Robin H. Johnson <robbat2@gentoo.org> wrote:

Show 8 quoted lines

> 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