On Wed, 12 Oct 2005, Borislav Petkov wrote:
>
> Hm, I think that this is even merged already, at least the exact same one liner
> I sent is in Linus' git (see commit id dd0fc66fb33cd610bc1a5db8a5e232d34879b4d7). By the way, how
> can you see the patch's source by using the commit id?
>
> git-cat-file "blob" dd0fc66fb33cd610bc1a5db8a5e232d34879b4d7
> says "bad file."
That's because it's not a blob ;)
You can do
git-cat-file -t dd0fc66
and it will tell you it's a "commit" object. Then do
git-cat-file commit dd0fc66
and it will show the actual commit internals, including commit info,
parents and what tree object that commit is associated with.
HOWEVER. What you actually want to see is probably
git-diff-tree -p --pretty dd0fc66
which shows the commit as "patch" (-p) and a "pretty header" (--pretty).
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
