From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Manual is out of date, missing commands and information
Date: Sun, 28 Jan 2018 22:57:44 +0100 [thread overview]
Message-ID: <20180128215744.12B612415A7@gemini.denx.de> (raw)
In-Reply-To: <CAGdamPDuwmr3Lqt+w6tZ4tdvH4VvtEmAcqqEnJ=T1-NWtmsGvg@mail.gmail.com>
Dear Nathan,
In message <CAGdamPDuwmr3Lqt+w6tZ4tdvH4VvtEmAcqqEnJ=T1-NWtmsGvg@mail.gmail.com> you wrote:
>
> So I wrote that when I thought there were better guides online somewhere. I
> haven't found any more complete guides. Maybe that is intentional?
Intentional? Not sure if you want to insinuate anything here, or
what. I think it's just a manifestation of the usual situation that
developers find it more interesting to hack on the code, and they
don't need much documentation because they live with the code day by
day - and the users, on the other hand, tend to complain only and
not contribute back.
> Surely there is some guide out there, either for free or not.
If you find anything better than the DULG please lt us know (or,
even better, help to improve the manual).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The last thing one knows in constructing a work is what to put first.
- Blaise Pascal
next prev parent reply other threads:[~2018-01-28 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 22:33 [U-Boot] Manual is out of date, missing commands and information Nathan Holder
2018-01-28 21:57 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 14:39 Nathan Holder
2018-01-27 19:54 ` Wolfgang Denk
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=20180128215744.12B612415A7@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.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