From: Lucas Stach <l.stach@pengutronix.de>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/9] Docs: just mark the 'bootm' command like the 'go' command as well
Date: Mon, 26 Jan 2015 11:50:10 +0100 [thread overview]
Message-ID: <1422269410.15206.2.camel@pengutronix.de> (raw)
In-Reply-To: <1422269200.15206.1.camel@pengutronix.de>
Am Montag, den 26.01.2015, 11:46 +0100 schrieb Lucas Stach:
> Am Montag, den 26.01.2015, 11:39 +0100 schrieb Juergen Borleis:
> > Just a try to be consistent in one sentence.
> >
> > Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
> > ---
> > Documentation/boards/mxs.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/boards/mxs.rst b/Documentation/boards/mxs.rst
> > index 6c8bdb5..879663c 100644
> > --- a/Documentation/boards/mxs.rst
> > +++ b/Documentation/boards/mxs.rst
> > @@ -115,5 +115,5 @@ mxsboot tool which changes this sector number in the image.
> > Booting second stage
> > --------------------
> >
> > -The second stage images can be started with the barebox bootm command or
> > +The second stage images can be started with the barebox 'bootm' command or
> > just jumped into using the 'go' command.
>
> Wouldn't it be better to directly link to those commands by
> using :ref:`command_bootm` (same for go), like in other parts of the
> documentation?
>
And I just noticed you do exactly that in Patch 5/9.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-26 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 10:39 A little bit fixing and extending the existing documentation Juergen Borleis
2015-01-26 10:39 ` [PATCH 1/9] Docs: just fix a typo Juergen Borleis
2015-01-26 10:39 ` [PATCH 2/9] Docs: just mark the 'bootm' command like the 'go' command as well Juergen Borleis
2015-01-26 10:46 ` Lucas Stach
2015-01-26 10:50 ` Lucas Stach [this message]
2015-01-26 10:39 ` [PATCH 3/9] Docs: add some info about the Ka-Ro TX25 related bootloader images Juergen Borleis
2015-01-26 10:39 ` [PATCH 4/9] Docs: add some info about the Phytec's phyCORE27 and phyCARD27 " Juergen Borleis
2015-01-26 10:39 ` [PATCH 5/9] Docs: extend the mentioned commands with a link to their documentation Juergen Borleis
2015-01-26 10:39 ` [PATCH 6/9] Docs: move the individual MXS target documentation where they belong to Juergen Borleis
2015-01-26 10:39 ` [PATCH 7/9] Docs: the name of the default config file for the FSL i.MX23 evk has changed Juergen Borleis
2015-01-26 10:39 ` [PATCH 8/9] Docs: extend the mentioned commands with a link to their documentation Juergen Borleis
2015-01-26 10:39 ` [PATCH 9/9] Docs: add some info about the Olimex's Olinuxino related bootloader images Juergen Borleis
2015-01-27 7:39 ` A little bit fixing and extending the existing documentation Sascha Hauer
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=1422269410.15206.2.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jbe@pengutronix.de \
/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