From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] manual: convert existing documentation to the asciidoc format
Date: Mon, 03 Oct 2011 18:49:55 +0200 [thread overview]
Message-ID: <4E89E7B3.6060406@lucaceresoli.net> (raw)
In-Reply-To: <d871cc9dcec1de13aa412736a1f5f1e6108b8b62.1317326629.git.thomas.petazzoni@free-electrons.com>
Hi Thomas,
I found a few minor issues that I report below.
In general, I really appreciate this job. BR is growing in features and
complexity, and a single HTML file is not enough anymore. Thanks!
Acked-by: Luca Ceresoli <luca@lucaceresoli.net>
Thomas Petazzoni wrote:
...
> +* *Makefiles for generic packages* (not using autotools): These
> + are based on an infrastructure similar to the one used for
> + autotools-based packages, but requires a little more work from the
> + developer. They specify what should be done for the configuration,
> + compilation, installation and cleanup of the package. This
> + infrastructure must be used for all packages that do not use the
> + autotools as their build system. In the future, other specialized
> + infrastructures might be written for other build systems.
> + We cover them through in xref:gentargets-tutorial[] and
> + xref:gentargets-reference[].
> +
These links do not work.
In the HTML output the link is:
<a href="#gentargets-reference">[gentargets-reference]</a>
but the target anchor is:
<h4 id="_tt_gentargets_tt_reference"><tt>GENTARGETS</tt>
Reference</h4>
In the PDF I read:
We cover them through in [?] and [?].
> +* *Makefiles for autotools-based software* (autoconf, automake,
> + etc.): We provide a dedicated infrastructure for such packages, since
> + autotools is a very common build system. This infrastructure<i>must
> +</i> be used for new packages that rely on the autotools as their
> + build system.<br/>We cover them through a
> +<a href="#autotools-tutorial">tutorial</a> and a
> +<a href="#autotools-reference">reference</a>.</li>
Here are some remnants of the original HTML, I guess.
There are others here and there, but it's trivial to find them by
searching for "<". Most hits are like this one.
Luca
next prev parent reply other threads:[~2011-10-03 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 20:05 [Buildroot] [pull request] Pull request for branch for-2011.11/asciidoc-manual Thomas Petazzoni
2011-09-29 20:05 ` [Buildroot] [PATCH 1/4] manual: convert existing documentation to the asciidoc format Thomas Petazzoni
2011-09-29 21:57 ` Yann E. MORIN
2011-10-03 16:49 ` Luca Ceresoli [this message]
2011-09-29 20:05 ` [Buildroot] [PATCH 2/4] manual: provide make targets to build the documentation Thomas Petazzoni
2011-09-29 21:53 ` Yann E. MORIN
2011-10-03 16:53 ` Luca Ceresoli
2011-09-29 20:06 ` [Buildroot] [PATCH 3/4] remove the old buildroot.html documentation Thomas Petazzoni
2011-09-29 21:59 ` Yann E. MORIN
2011-09-29 20:06 ` [Buildroot] [PATCH 4/4] remove Glibc_vs_uClibc document Thomas Petazzoni
2011-09-29 21:59 ` Yann E. MORIN
2011-10-03 16:54 ` Luca Ceresoli
2011-09-30 6:36 ` [Buildroot] [pull request] Pull request for branch for-2011.11/asciidoc-manual Peter Korsgaard
2011-09-30 6:38 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2011-10-10 8:46 [Buildroot] [pull request v4] " Thomas Petazzoni
2011-10-10 8:46 ` [Buildroot] [PATCH 1/4] manual: convert existing documentation to the asciidoc format Thomas Petazzoni
2011-10-10 9:00 ` Thomas De Schampheleire
2011-10-25 10:12 ` Peter Korsgaard
2011-08-31 21:54 [Buildroot] [pull request v2] Pull request for branch for-2011.11/asciidoc-manual Thomas Petazzoni
2011-08-31 21:54 ` [Buildroot] [PATCH 1/4] manual: convert existing documentation to the asciidoc format Thomas Petazzoni
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=4E89E7B3.6060406@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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