From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH 1/4] doc: fix xref link from api docs to manual pages
Date: Mon, 4 Jun 2012 22:17:41 +0200 [thread overview]
Message-ID: <1338841064-32294-1-git-send-email-Matthieu.Moy@imag.fr> (raw)
In-Reply-To: <1338739804-32167-1-git-send-email-Matthieu.Moy@imag.fr>
From: Junio C Hamano <gitster@pobox.com>
They are one-level above, so refer them as linkgit:../git-foo[n] with "../"
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
That's Junio's patch unmodified (I took it at the beginning of the
serie so that my linkgit:../ isn't the fist to appear)
Documentation/technical/api-config.txt | 2 +-
Documentation/technical/api-merge.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/technical/api-config.txt b/Documentation/technical/api-config.txt
index edf8dfb..bd4d8b8 100644
--- a/Documentation/technical/api-config.txt
+++ b/Documentation/technical/api-config.txt
@@ -2,7 +2,7 @@ config API
==========
The config API gives callers a way to access git configuration files
-(and files which have the same syntax). See linkgit:git-config[1] for a
+(and files which have the same syntax). See linkgit:../git-config[1] for a
discussion of the config file syntax.
General Usage
diff --git a/Documentation/technical/api-merge.txt b/Documentation/technical/api-merge.txt
index 9dc1bed..25158b8 100644
--- a/Documentation/technical/api-merge.txt
+++ b/Documentation/technical/api-merge.txt
@@ -36,7 +36,7 @@ the operation of a low-level (single file) merge. Some options:
ancestors in a recursive merge.
If a helper program is specified by the
`[merge "<driver>"] recursive` configuration, it will
- be used (see linkgit:gitattributes[5]).
+ be used (see linkgit:../gitattributes[5]).
`variant`::
Resolve local conflicts automatically in favor
--
1.7.11.rc0.57.g84a04c7
next prev parent reply other threads:[~2012-06-04 20:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 16:10 [PATCH 0/3] Improve credential API documentation Matthieu Moy
2012-06-03 16:10 ` [PATCH 1/3] api-credential.txt: show the big picture first Matthieu Moy
2012-06-04 11:51 ` Jeff King
2012-06-03 16:10 ` [PATCH 2/3] api-credentials.txt: mention credential.helper explicitly Matthieu Moy
2012-06-04 11:54 ` Jeff King
2012-06-04 17:51 ` Matthieu Moy
2012-06-03 16:10 ` [PATCH 3/3] api-credentials.txt: add "see also" section Matthieu Moy
2012-06-03 22:28 ` Junio C Hamano
2012-06-04 11:31 ` Matthieu Moy
2012-06-04 11:56 ` Jeff King
2012-06-04 19:31 ` Junio C Hamano
2012-06-04 20:06 ` Matthieu Moy
2012-06-05 6:59 ` Jeff King
2012-06-05 7:34 ` Jeff King
2012-06-05 11:20 ` Matthieu Moy
2012-06-05 11:22 ` Jeff King
2012-06-05 15:12 ` Junio C Hamano
2012-06-05 15:35 ` Jeff King
2012-06-05 17:28 ` Junio C Hamano
2012-06-04 20:17 ` Matthieu Moy [this message]
2012-06-04 20:17 ` [PATCH 2/4 v2] api-credential.txt: show the big picture first Matthieu Moy
2012-06-05 7:36 ` Jeff King
2012-06-04 20:17 ` [PATCH 3/4 v2] api-credentials.txt: mention credential.helper explicitly Matthieu Moy
2012-06-04 20:17 ` [PATCH 4/4 v2] api-credentials.txt: add "see also" section Matthieu Moy
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=1338841064-32294-1-git-send-email-Matthieu.Moy@imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).