Re: [PATCH] git-cget: prints elements of C code in the git repository

From: Mike Ralphson <mike.ralphson@gmail.com>
Date: Mar 24, 2009, 16:37 UTC
Message-ID: <e2b179460903240937p58dff7e8u238fbe06785cdb77@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0903241555360.7493@intel-tinevez-2-302>

2009/3/24 Johannes Schindelin <Johannes.Schindelin@gmx.de>:

Show 5 quoted lines

>> This kind of pipeline has the benefit that it can actually work on the
>> *repository*, and not just the working copy (as per the posted script).
>
> Did I miss something?  git ls-files pipes only the names to xargs, not the
> full contents, right?

See where I wrote "this kind of pipeline" vs "git ls-files" which was just quoting Peff? 8-)

I dunno, maybe C folk using git would only be interested in the index/working copy, but that tells me this script is even more tenuously linked to git. We don't bundle a compiler just because it can use git ls-files to work out what to compile...

The script might be best as a standalone tool which just happened to take advantage of the VCS in use by reacting to its surroundings. Then it would also be useful by hg, svn, cvs people etc.

If it actually used the information in the repository to be able to run git blame on the definitions, or show a git log -p style list of changes in the definition, that might be different.

Mike