From: Lucas Stach <l.stach@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: New Documentation for barebox
Date: Thu, 26 Jun 2014 12:01:22 +0200 [thread overview]
Message-ID: <1403776882.4254.7.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <CAOpc7mHfA9VTobbpW8SecSorV5K0KrESn75T4ue-Y0iGs9j=qw@mail.gmail.com>
Am Donnerstag, den 26.06.2014, 11:54 +0200 schrieb Holger Schurig:
> Oh, and I just noticed that two chapters "Getting barebox" are contained:
>
> 1. Getting barebox
> 3.1. Getting barebox
>
> I'd also think that long-term the "user manual" thingy inside the
> documention could vanish. Everything could/should/is the user manual,
> or?
>
No, we would like to clearly separate user docs as in how to get barebox
running on a board and what to do in the shell from developer docs that
explain some of the concepts and design decisions of the actual code.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-26 10:03 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
2014-06-26 18:17 ` Sascha Hauer
2014-06-26 9:54 ` Holger Schurig
2014-06-26 10:01 ` Lucas Stach [this message]
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=1403776882.4254.7.camel@weser.hi.pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
/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