From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: New Documentation for barebox
Date: Thu, 26 Jun 2014 17:36:48 +0200 [thread overview]
Message-ID: <20140626153648.GB14257@pengutronix.de> (raw)
In-Reply-To: <20140626142827.ade227cb4fa1909f4267a9c0@gmail.com>
On Thu, Jun 26, 2014 at 02:28:27PM +0400, Antony Pavlov wrote:
> On Thu, 26 Jun 2014 10:51:31 +0200
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> > Hi all,
> >
> > I am happy to announce new documentation for barebox.
>
> Aghhhh!
>
> All my mips documentation have gone away!
Sorry, that was not intentional. I won't merge the branch until the mips
documentation is back.
>
> I'm ready to convert old dox-files to new rst-files by myself,
> but I need some recomendations.
>
> Could I put rst mips files into Documentation/boards/mips?
Sure, whatever suits best for you. For i.MX it makes sense to have some
i.MX document describing the common i.MX stuff. I don't know enough
about MIPS to know if it's best to have SoC type or generic MIPS docs.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-26 15:37 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
2014-06-26 10:11 ` Holger Schurig
2014-06-26 10:28 ` Antony Pavlov
2014-06-26 15:36 ` Sascha Hauer [this message]
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=20140626153648.GB14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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