On 12/14/21 5:38 AM, Richard Purdie wrote:
On Tue, 2021-12-14 at 11:27 +0000, Ross Burton wrote:
On Tue, 14 Dec 2021 at 10:38, Alexander Kanavin <[email protected]> wrote:
On Tue, 14 Dec 2021 at 11:30, Michael Opdenacker
<[email protected]> wrote:
Are you suggesting to expand the official Yocto Project docs on this topic?
Actually, I only see
https://docs.yoctoproject.org/dev-manual/common-tasks.html#patching-code
which explains the use of patches. There is much more content indeed in
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
I would suggest you link to the wiki, but please do not copy any content, as it
will certainly become mismatched.
I'd actually suggest the proper documentation is improved, and the
wiki page retired. Wikis are great for getting something written
down, but if the proper documentation can have a chapter, then that's
even better.
I was thinking something similar, I think we should document this in the proper
documentation and then the wiki can refer to it. Wikis are good to a point and
great at pulling info together but not a substitute for the docs.
This was originally done in wiki format, because the expectation is that it
would change. Whatever the current version documented was the patch format
expected. By adding it to the 'project documentation', people may believe that
when submitting to gatesgarth you must conform to gatesgarth, hardknot whatever
was documented in hardknot, and so forth. That was not my intention, it was
also supposed to be "write your patch/commit to conform to the current
specification."
--Mark
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1406):
https://lists.openembedded.org/g/openembedded-architecture/message/1406
Mute This Topic: https://lists.openembedded.org/mt/87718475/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
