one more lightweight vote in favor.... such a feature would eliminate a few shell scripts i cobbled together which essentially allow me to say git diff 8a6352:path/to/module 5f3461:moved/and/hacked/copy On Tuesday 18 April 2006 18:21, Shawn Pearce wrote: > Not that my voice carries much weight, but a coworker has been > asking for this feature to be added to pg for months. I've just > been too lazy to get around to writing the shell code to do it. > Making it part of git cat-file seems like a good idea, making it > usable by other tools like git diff just rocks. :-) > > I think its a very worthwhile addition. > > Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > > On 4/19/06, Linus Torvalds <torvalds@xxxxxxxx> wrote: > > > What do people think? Have you ever wanted to > > > access individual files in some random revision? Do you think this is > > > useful? > > > > Definitely, I've several times had to go through contortions to do > > this easily, and I've ended up turning to gitweb often to quickly see > > the state of a file at a given revision. > > > > > With this, you can do something like > > > > > > git cat-file blob v1.2.4:Makefile > > > > > > to get the contents of "Makefile" at revision v1.2.4. > > > > > > Now, this isn't necessarily something you really need all that often, > > > but the concept itself is actually pretty powerful. We could, for > > > example, allow things like > > > > > > git diff v0.99.6:git-commit-script..v1.3.0:git-commit.sh > > > > These two examples are more than enough -- I buy ;-) - : 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