public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	JPEWhacker@gmail.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [RFC 0/1] initial documentation for hash equivalence
Date: Fri, 18 Jun 2021 18:59:48 +0200	[thread overview]
Message-ID: <b8c98536-c720-a5ba-3e27-cac5b34e2fd2@bootlin.com> (raw)
In-Reply-To: <e0fbf82a03bef065ed381299a7c38d5f9a47932e.camel@linuxfoundation.org>

Hi Richard,

Many thanks for your answers to my questions!

On 6/17/21 10:47 PM, Richard Purdie wrote:
> We definitely need a high level overview so people can understand what it 
> is doing. I suspect we'll need this and some more in depth docs too.

Right, this makes sense.

>
>>   Would I need to add more details about the implementation,
>>   such as using explaining unihashes and adding diagrams such
>>   as the ones in Joshua Watt's presentation on the topic?
> People will need to know more about it so I do think further manual 
> sections on topics like that will be needed, yes.


Ok, will do :)

>> - Doesn't this need a more thorough update of the whole
>>   documentation about share state cache to give the new
>>   full picture right away, rather than adding this new
>>   feature later in the manual ?
> We do need to update other sections and tie this in, yes.


Yes, I suspected that. Thanks for confirming. I'll see what I can do.

>
>> - Anything else that I should mention?
> There is a read only mode and pass through for the server which will be 
> needed. We need to document how to launch a standalone server instance?


Good to know. I'll investigate it.

Thanks again!

Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2021-06-18 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 19:55 [RFC 0/1] initial documentation for hash equivalence Michael Opdenacker
2021-06-17 19:55 ` [RFC 1/1] overview-manual: " Michael Opdenacker
2021-06-17 20:40   ` [docs] " Richard Purdie
2021-06-18 16:55     ` Michael Opdenacker
2021-06-17 20:47 ` [docs] [RFC 0/1] " Richard Purdie
2021-06-18 16:59   ` Michael Opdenacker [this message]

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=b8c98536-c720-a5ba-3e27-cac5b34e2fd2@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=JPEWhacker@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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