mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: New Documentation for barebox
Date: Thu, 26 Jun 2014 11:36:15 +0200	[thread overview]
Message-ID: <CAOpc7mEXX4GQh2oxGO1y7Y8bNsgf=DZzOwc9aBZwToftk=vv8w@mail.gmail.com> (raw)
In-Reply-To: <1403772698-10330-1-git-send-email-s.hauer@pengutronix.de>

Some random annotations. Please comment, after feedback I'll provide a
bunch of patches for this. I don't do the patches right away, because
you may still work currently in that area, so it would only produce
conflicts.


User manuel "2. System setup" should be in an appendix. Nothing here
is really related to barebox itself. It contains just helpful hints.

I would capitalize some headlines, e.g. in the user manual "3.
Barebox", "4. Networking", "6. Memory areas" etc   The same for the
two headlines starting in lower-case in the main index.html. Maybe "3.
barebox" can stay lowercase, because barebox is an "Eigenname", dunno.
It looks however a bit ugly when it's lowercase.

After getting barebox there should be a brief mention of the branches,
e.g. difference between next & master.

Configuration: at "make menuconfig" also "make xconfig" should be mentioned.

"3.3. Compilation", shouldn't it be "make ARCH=xxx" ?  Ha, maybe it's
just an old habit of me ...

"3.4 Starting Barebox" could get a link to the i.MX USB downloader.
Very fine tool!

"4.2. Network filesystems": hinting on automount for tftp-file system
is a bit moot. Because at the "mount -t tftp AAA BBB" nothing happens,
tftp is, so to say, an automount by itself. I haven't yet used NFS
from barebox, but I guess it is the same there. So I'd remove the
automount reference from this place completely.

"5. Automount", the same, better use sdcard as an example,. not tftp.

"7.2. Device parameters": Better write "HINT: barebox has ..." (e.g.
with a colon). The same applies to the "NOTE" annotations.

"8.1 Hush features" should "let X=$A/2" be there?  Many people (ok, it
was just me) look there if they need to calculate in the shell after
finding out that X=$(($A/2)) doesn't work ...

"10. Configuration variable": this should be neared the device
parameters. I'd add a hint that with "devinfo global" one can see all
defined global variables.

several places: the "barebox@Genesi Efika MX Smartbook:/" should be
reduced to "barebox:/", as it is usually irrelevant if that example
was done on an Efika board or not.

"11. Updating barebox", it says that a board can register an update
handler, but doesn't have an example or a link to where / how this
could be done. Or even a link directly to the git tree with a working
example.

"13. Prebootloader": the sentence "Use the barebox-flash-image link
which always points to the correct image" doesn't sound like proper
english.


Abbreviation should be capizalized as well, therefore headline "ram
filesystem" -> "RAM filesystem"

I think that in english one should write "file systems", not
"filesystems". But i may be wrong. But I'm quite sure that the word
"filesystemtype" (in the RAM file system chapter) is too long for any
englishman :-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-06-26  9:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26  8:51 Sascha Hauer
2014-06-26  8:51 ` [PATCH 1/7] ubiformat: avoid macros in help text Sascha Hauer
2014-06-26  8:51 ` [PATCH 2/7] automount: fix description typo Sascha Hauer
2014-06-26  8:51 ` [PATCH 3/7] commands: addpart: Improve description Sascha Hauer
2014-06-26  8:51 ` [PATCH 4/7] Documentation: remove doxygen documentation Sascha Hauer
2014-06-26  8:51 ` [PATCH 5/7] Documentation: remove remaining documentation Sascha Hauer
2014-06-26  8:51 ` [PATCH 6/7] Documentation: remove devicetree docs Sascha Hauer
2014-06-26  8:51 ` [PATCH 7/7] Documentation: Add new sphinxs docs Sascha Hauer
2014-06-26  9:02 ` New Documentation for barebox Holger Schurig
2014-06-26  9:09   ` Sascha Hauer
2014-06-26  9:36 ` Holger Schurig [this message]
2014-06-26 18:17   ` Sascha Hauer
2014-06-26  9:54 ` Holger Schurig
2014-06-26 10:01   ` Lucas Stach
2014-06-26 10:11     ` Holger Schurig
2014-06-26 10:28 ` Antony Pavlov
2014-06-26 15:36   ` Sascha Hauer
2014-06-26 10:31 ` Robert P. J. Day
2014-06-26 18:56   ` 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='CAOpc7mEXX4GQh2oxGO1y7Y8bNsgf=DZzOwc9aBZwToftk=vv8w@mail.gmail.com' \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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