From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Geoffrey Irving <irving@naml.us>, git@vger.kernel.org
Subject: Re: cherry picking changesets instead of commits
Date: Wed, 28 May 2008 18:48:19 -0400 [thread overview]
Message-ID: <20080528224819.GA15252@sigill.intra.peff.net> (raw)
In-Reply-To: <20080528223858.GA15107@sigill.intra.peff.net>
On Wed, May 28, 2008 at 06:38:58PM -0400, Jeff King wrote:
> which will turn it into the text you wrote for a manpage, or a link in
> the HTML version. Looks like we already have a few of the style you used
> that should probably be fixed, though.
Actually, it looks like there is only one; patch is below. There are a
few false positives in gitk.txt, but they point to projects outside of
core git (like qgit, gitview, and tig), and so must be left as straight
text.
-- >8 --
doc/git-gui: make gitk "see also" a link
Even though git-gui and gitk are both maintained separately,
the documentation is part of core git, and thus it makes
sense to use the linkgit macro to create an href in the HTML
documentation.
---
Documentation/git-gui.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt
index 6d6cd5d..cf2541f 100644
--- a/Documentation/git-gui.txt
+++ b/Documentation/git-gui.txt
@@ -81,7 +81,7 @@ git gui browser maint::
See Also
--------
-'gitk(1)'::
+linkgit:gitk[1]::
The git repository browser. Shows branches, commit history
and file differences. gitk is the utility started by
git-gui's Repository Visualize actions.
--
1.5.6.rc0.143.ge5cbe0
next prev parent reply other threads:[~2008-05-28 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 18:06 cherry picking changesets instead of commits Geoffrey Irving
2008-05-28 18:19 ` Junio C Hamano
2008-05-28 18:28 ` Geoffrey Irving
2008-05-28 18:46 ` Junio C Hamano
2008-05-28 19:42 ` Geoffrey Irving
2008-05-28 20:46 ` Junio C Hamano
2008-05-28 21:14 ` Geoffrey Irving
2008-05-28 22:38 ` Jeff King
2008-05-28 22:48 ` Jeff King [this message]
2008-05-28 23:56 ` Junio C Hamano
2008-05-29 0:12 ` Jeff King
2008-05-29 0:04 ` [PATCH] Documentation: git-cherry uses git-patch-id Junio C Hamano
2008-05-29 0:07 ` Geoffrey Irving
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=20080528224819.GA15252@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=irving@naml.us \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).