Re: cherry picking changesets instead of commits
- From
Jeff King <peff@peff.net>
- Date
- May 28, 2008, 22:48 UTC
- Message-ID
- <20080528224819.GA15252@sigill.intra.peff.net>
- 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