From: bfields@fieldses.org
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 1/5] documentation: mention gitk font adjustment in tutorial
Date: Mon, 29 May 2006 19:31:32 -0400 [thread overview]
Message-ID: <11489454961705-git-send-email-bfields@fieldses.org> (raw)
From: J. Bruce Fields <bfields@citi.umich.edu>
Kind of silly, but the font I get by default in gitk makes it mostly
unusable for me, so this is the first thing I'd want to know about.
(But maybe there's a better suggestion than just Ctrl-='ing until
satisfied.)
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
ded59a62d1d7b114cdc4d5352e89006880e94f08
Documentation/tutorial.txt | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
ded59a62d1d7b114cdc4d5352e89006880e94f08
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 79781ad..5fdeab9 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -429,7 +429,9 @@ visualizing their history. For example,
-------------------------------------
allows you to browse any commits from the last 2 weeks of commits
-that modified files under the "drivers" directory.
+that modified files under the "drivers" directory. (Note: you can
+adjust gitk's fonts by holding down the control key while pressing
+"-" or "+".)
Finally, most commands that take filenames will optionally allow you
to precede any filename by a commit, to specify a particular version
--
1.3.3.gff62
next 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 bfields [this message]
2006-05-29 23:31 ` [PATCH 2/5] documentation: add brief mention of cat-file to tutorial part I bfields
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=11489454961705-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.