From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Owen Hilyard <ohilyard@iol.unh.edu>, dev <dev@dpdk.org>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [RFC] DTS Commit Policies
Date: Mon, 17 Jan 2022 12:23:36 +0000 [thread overview]
Message-ID: <dcb43bd4fb354e598f46721eb29767f6@pantheon.tech> (raw)
In-Reply-To: <CAHx6DYCFDVCOmmDpy3n9XOG9-mvMWtdZqmkcnk3xWv1Mh87PFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
From: Owen Hilyard <ohilyard@iol.unh.edu>
Sent: Wednesday, January 12, 2022 4:08 PM
To: dev <dev@dpdk.org>; dts@dpdk.org
Subject: [RFC] DTS Commit Policies
Hello Everyone,
The DTS Working Group wanted to let everyone give feedback on the proposed DTS commit policies. Please leave a comment with any feedback you have. We will be reviewing feedback in the DTS Working Group meeting on January 26th, at which point the comment period will close.
The purpose of the commit policies is to help standardize the code that makes up DTS, as well as help new additions meet community requirements, such as avoiding breaking changes, ensuring runtime stability, and aiding debugability.
Owen Hilyard
DTS Working Group meeting room: https://armltd.zoom.us/j/97503259680?pwd=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon
I always like to follow the practices captured in this article: https://cbea.ms/git-commit/
I think it also makes sense to be as close as possible to DPDK, so trying to use what we can from their guidelines [0] would be a good start.
Juraj
[0] https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-subject-line
[-- Attachment #2: Type: text/html, Size: 5869 bytes --]
next prev parent reply other threads:[~2022-01-17 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 15:08 Owen Hilyard
2022-01-17 12:23 ` Juraj Linkeš [this message]
2022-01-18 14:30 ` Owen Hilyard
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=dcb43bd4fb354e598f46721eb29767f6@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).