From: bfields@fieldses.org
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 2/5] documentation: add brief mention of cat-file to tutorial part I
Date: Mon, 29 May 2006 19:31:33 -0400 [thread overview]
Message-ID: <1148945496592-git-send-email-bfields@fieldses.org> (raw)
In-Reply-To: <11489454961705-git-send-email-bfields@fieldses.org>
From: J. Bruce Fields <bfields@citi.umich.edu>
I'd rather avoid git cat-file so early on, but the
git-cat-file -p old-commit:/path/to/file
trick is too useful....
Also fix a nearby typo while we're at it.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
e47d8a459f0a2407304c9b7165b30746baa7fe29
Documentation/tutorial.txt | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
e47d8a459f0a2407304c9b7165b30746baa7fe29
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 5fdeab9..039a859 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -435,12 +435,18 @@ adjust gitk's fonts by holding down the
Finally, most commands that take filenames will optionally allow you
to precede any filename by a commit, to specify a particular version
-fo the file:
+of the file:
-------------------------------------
$ git diff v2.5:Makefile HEAD:Makefile.in
-------------------------------------
+You can also use "git cat-file -p" to see any such file:
+
+-------------------------------------
+$ git cat-file -p v2.5:Makefile
+-------------------------------------
+
Next Steps
----------
--
1.3.3.gff62
next prev parent reply other threads:[~2006-05-29 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 23:31 [PATCH 1/5] documentation: mention gitk font adjustment in tutorial bfields
2006-05-29 23:31 ` bfields [this message]
2006-05-29 23:31 ` [PATCH 3/5] Documentation: retitle the git-core tutorial bfields
2006-05-29 23:31 ` [PATCH 4/5] Documentation: rewrite the core-tutorial introduction bfields
2006-05-29 23:31 ` [PATCH 5/5] Documentation: fix a tutorial-2 typo bfields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1148945496592-git-send-email-bfields@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.