From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/9] manual: fix cross-refs
Date: Thu, 14 Feb 2013 07:46:44 +0100 [thread overview]
Message-ID: <511C8854.7070806@mind.be> (raw)
In-Reply-To: <e90370a2ea8deb23fd0d2c058f251d702f6bb783.1360795941.git.s.martin49@gmail.com>
On 13/02/13 23:59, Samuel Martin wrote:
> diff --git a/docs/manual/working-with.txt b/docs/manual/working-with.txt
> index b69d1e2..a57169c 100644
> --- a/docs/manual/working-with.txt
> +++ b/docs/manual/working-with.txt
> @@ -25,4 +25,5 @@ interested in hacking it to add:
>
> * new packages: refer to the xref:adding-packages[Developer guide]
>
> -* new board support: refer to the xref:board-support[Developer guide]
> +* new board support: refer to the xref:customize-store[], more specifically
> + xref:customize-store-board-support[].
I haven't checked, but doesn't this render to something like "refer to
the 3.4, more specifically 3.7"? Why not just:
* new board support: refer to the
xref:customize-store-board-support[Developer guide].
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-02-14 6:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 22:59 [Buildroot] [pull request] Pull request for branch for-master/doc Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 1/9] manual: cleanup and update editor tags Samuel Martin
2013-02-14 6:47 ` Arnout Vandecappelle
2013-02-17 21:50 ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 2/9] manual: fix cross-refs Samuel Martin
2013-02-14 6:46 ` Arnout Vandecappelle [this message]
2013-02-13 22:59 ` [Buildroot] [PATCH 3/9] manual: sprinkle with some calls to MESSAGE Samuel Martin
2013-02-14 6:48 ` Arnout Vandecappelle
2013-02-17 21:51 ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 4/9] manual: faq: add entry about the relocatable toolchain Samuel Martin
2013-02-14 6:49 ` Arnout Vandecappelle
2013-02-14 17:32 ` Thomas Petazzoni
2013-02-23 13:33 ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 5/9] manual: faq: add workaround to avoid rebuilding the buildroot toolchain after each clean Samuel Martin
2013-02-14 7:04 ` Arnout Vandecappelle
2013-02-14 17:36 ` Thomas Petazzoni
2013-02-23 13:34 ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 6/9] manual: minor fix in patch-policy.txt Samuel Martin
2013-02-14 7:06 ` Arnout Vandecappelle
2013-02-14 17:37 ` Thomas Petazzoni
2013-02-17 21:54 ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 7/9] manual: misc. post-{build, image} scripts fixes Samuel Martin
2013-02-14 7:16 ` Arnout Vandecappelle
2013-02-13 22:59 ` [Buildroot] [PATCH 8/9] manual: update {deprecated, package}-list.txt Samuel Martin
2013-02-18 7:23 ` Arnout Vandecappelle
2013-02-25 21:22 ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 9/9] Makefile: add to the release target a warning about the manual updates Samuel Martin
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=511C8854.7070806@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox