All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: Tim Orling <ticotimo@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [sphinx] updates as of Sep 10th.
Date: Tue, 15 Sep 2020 18:48:24 +0200	[thread overview]
Message-ID: <CAP71WjxQNormFOzCsd5h3MopO4hTdn5ENgU_Wmt+UdwPJ0jQog@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-D1W=S8Jz=b6_d+D3frcqpZQkhmSHW=ZCjZ4tUMGWWpyQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2702 bytes --]

On Tue, Sep 15, 2020 at 5:44 PM Tim Orling <ticotimo@gmail.com> wrote:

>
>
> On Mon, Sep 14, 2020 at 3:05 PM Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
>
>>
>>
>> On Mon, Sep 14, 2020 at 5:26 PM Richard Purdie <
>> richard.purdie@linuxfoundation.org> wrote:
>>
>>> On Mon, 2020-09-14 at 09:50 +0100, Richard Purdie via
>>> lists.yoctoproject.org wrote:
>>> > On Sun, 2020-09-13 at 16:42 +0100, Richard Purdie via
>>> > lists.yoctoproject.org wrote:
>>> > > On Fri, 2020-09-11 at 00:03 +0200, Nicolas Dechesne wrote:
>>> > > > If anybody has any cycle now, we need to finish #4. The current
>>> > > > status is that:
>>> > > > * brief-yoctoprojectqs/* is done.
>>> > > > * bitbake user manual is half done, and I am doing it
>>> > > > * bsp-guide/*: i started it, and will finish
>>> > > > * ref-manual/*: RP is on it.
>>> > >
>>> > > This is done, at least as a first pass with hopefully the bulk of
>>> > > issues fixed.
>>> > >
>>> > > > * there are plenty of warnings when we build, i would like to get
>>> > > > rid
>>> > > > of them all!
>>> > > >
>>> > > > Anything else is work that remains to be done. Before starting
>>> > > > anything, please send a quick email here to let everyone know, to
>>> > > > avoid duplication. If you have any improvement, please share your
>>> > > > patches, I will take them into the sphinx/master branch. And I
>>> > > > will
>>> > > > continue to work on the remaining files that no one would pick.
>>> > >
>>> > > I'll take dev-manual/* next.
>>> >
>>> > dev-manual is on the branch, I'll look at sdk-manual next.
>>>
>>> sdk-manual is on the branch, kernel-dev is my next target.
>>>
>>
>> I am now done with bsp-guide and bitbake.  Based on Richard's last
>> comment, the remaining docs to process are:
>> overview-manual
>> profile-manual
>> test-manual
>> toaster-manual
>>
>> They are rather 'small' books. I believe Armin is looking at
>> overview-manual and Mark at test-manual. I will take profile-manual next.
>>
>
> I'll take a crack at toaster-manual today.
>

thanks!

I've finished profile-manual today. And excluded adt-manual from Sphinx
(deprecated doc). At this point, we have:
Richard on kernel-dev
Mark on test-manual
Armin on overview-manual
Tim on toaster-manual

Which means everything is now covered! Please send patches on the list for
review, and if you have any trouble with Sphinx , let me know!



> --Tim
>
>>
>> I've also updated https://docs.yoctoproject.org/ with all the latest
>> changes combined. If you can use the new website and report any issues,
>> please let us know.
>>
>>
>>> Cheers,
>>>
>>> Richard
>>>
>>> 
>>
>

[-- Attachment #2: Type: text/html, Size: 4798 bytes --]

  reply	other threads:[~2020-09-15 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 22:03 [sphinx] updates as of Sep 10th Nicolas Dechesne
2020-09-10 23:39 ` [docs] " akuster
2020-09-11  6:02   ` Nicolas Dechesne
2020-09-13 15:42 ` Richard Purdie
     [not found] ` <16346239585A567B.3515@lists.yoctoproject.org>
2020-09-14  8:50   ` Richard Purdie
     [not found]   ` <16349A56620CF0CB.7642@lists.yoctoproject.org>
2020-09-14 15:26     ` Richard Purdie
2020-09-14 22:05       ` Nicolas Dechesne
2020-09-15 15:44         ` Tim Orling
2020-09-15 16:48           ` Nicolas Dechesne [this message]
2020-09-15 22:17             ` Richard Purdie
2020-09-15 22:25               ` Tim Orling

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=CAP71WjxQNormFOzCsd5h3MopO4hTdn5ENgU_Wmt+UdwPJ0jQog@mail.gmail.com \
    --to=nicolas.dechesne@linaro.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ticotimo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.