git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Michael J Gruber <git@drmicha.warpmail.net>
Subject: [PATCH/RFC 4/6] convert doc links for other pages
Date: Fri, 12 Sep 2008 12:55:24 +0200	[thread overview]
Message-ID: <1221216926-20435-6-git-send-email-git@drmicha.warpmail.net> (raw)
In-Reply-To: <1221216926-20435-5-git-send-email-git@drmicha.warpmail.net>

This converts the doc links for pages which do not start with git:
"everyday" and "curl"
We use the "linkgitasis" macro which preserves their name.

Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
 Documentation/config.txt           |    2 +-
 Documentation/gitcore-tutorial.txt |    2 +-
 Documentation/gitglossary.txt      |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index fe71aba..102ee48 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -801,7 +801,7 @@ help.autocorrect::
 
 http.proxy::
 	Override the HTTP proxy, normally configured using the 'http_proxy'
-	environment variable (see linkgit:curl[1]).  This can be overridden
+	environment variable (see linkgitasis:curl[1]).  This can be overridden
 	on a per-remote basis; see remote.<name>.proxy
 
 http.sslVerify::
diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index 579e2b2..af44361 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -1691,7 +1691,7 @@ to follow, not easier.
 SEE ALSO
 --------
 linkgitasis:gittutorial[7], linkgitasis:gittutorial-2[7],
-linkgit:everyday[7], linkgitasis:gitcvs-migration[7],
+linkgitasis:everyday[7], linkgitasis:gitcvs-migration[7],
 link:user-manual.html[The Git User's Manual]
 
 GIT
diff --git a/Documentation/gitglossary.txt b/Documentation/gitglossary.txt
index 14c13fa..73aee50 100644
--- a/Documentation/gitglossary.txt
+++ b/Documentation/gitglossary.txt
@@ -17,7 +17,7 @@ include::glossary-content.txt[]
 SEE ALSO
 --------
 linkgitasis:gittutorial[7], linkgitasis:gittutorial-2[7],
-linkgit:everyday[7], linkgitasis:gitcvs-migration[7],
+linkgitasis:everyday[7], linkgitasis:gitcvs-migration[7],
 link:user-manual.html[The Git User's Manual]
 
 GIT
-- 
1.6.0.1.308.gede4c

  reply	other threads:[~2008-09-12 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 10:55 [PATCH/RFC 0/6] Documentation: use dashless links Michael J Gruber
2008-09-12 10:55 ` [PATCH/RFC 1/6] modified asciidoc macros for dashless git doc Michael J Gruber
2008-09-12 10:55   ` [PATCH/RFC 2/6] convert doc links for server type programmes from linkgit to gitlink Michael J Gruber
2008-09-12 10:55     ` [PATCH/RFC 2/6] convert doc links for server type programmes Michael J Gruber
2008-09-12 10:55       ` [PATCH/RFC 3/6] convert doc links for non-dashed git commands Michael J Gruber
2008-09-12 10:55         ` Michael J Gruber [this message]
     [not found]           ` <1221216926-20435-7-git-send-email-git@drmicha.warpmail.net>
2008-09-12 10:55             ` [PATCH/RFC 6/6] adjust the command lists (by category) to the new doc link macros Michael J Gruber
2008-09-12 11:32     ` [PATCH/RFC 2/6] convert doc links for server type programmes from linkgit to gitlink Michael J Gruber

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=1221216926-20435-6-git-send-email-git@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /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).