On Mon, Aug 30, 2010 at 6:55 AM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: > > ...because "ls-tree" lists the complete tree at the given revision, not > just the files changed in a commit. In fact, strictly speaking "ls-tree" > does not even operate on revisions but tree identifiers - given a > revision, it is resolved into a tree. > > You want to use something like "git diff --name-only oldrev newrev" or > another variant from the diff family. > > Michael That's great, thanks! That gets me the file names. Now, how do I get to the contents of each file? Do I have to do a git ls-tree and parse the contents, paying attention to only the files listed out with the git diff --name-only? I'm guessing there's a simpler way. Git show <newref> prints out all the diffs for that commit, but I need to examine the entire file. Thanks so much for the response! -Chris -- Christopher Patti - Geek At Large | GTalk: cpatti@xxxxxxxxx | AIM: chrisfeohpatti | P: (260) 54PATTI "Technology challenges art, art inspires technology." - John Lasseter, Pixar -- 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