summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS.md
diff options
context:
space:
mode:
authorSandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>2023-03-14 15:20:48 -0600
committerMark Hatle <mark.hatle@amd.com>2023-04-10 09:03:22 -0700
commitcf7f455e16ba259b0a42bb21d263900922b9f35e (patch)
tree4b042d2d21fb07fc620382c3ce2a7b2632234d2e /MAINTAINERS.md
parent53e60833cff3418236615a072d502e6003959485 (diff)
downloadmeta-xilinx-cf7f455e16ba259b0a42bb21d263900922b9f35e.tar.gz
MAINTAINERS: Fix mailing list email
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Diffstat (limited to 'MAINTAINERS.md')
-rw-r--r--MAINTAINERS.md15
1 files changed, 13 insertions, 2 deletions
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index 6a61ba3b..d9067769 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -6,14 +6,25 @@ the [meta-xilinx mailing list](https://lists.yoctoproject.org/g/meta-xilinx):
6 meta-xilinx@lists.yoctoproject.org 6 meta-xilinx@lists.yoctoproject.org
7 7
8When sending patches, please make sure the email subject line includes 8When sending patches, please make sure the email subject line includes
9"[meta-xilinx][PATCH]" and cc'ing the maintainers. 9`[meta-xilinx][<BRANCH_NAME>][PATCH]` and cc'ing the maintainers.
10 10
11For more details follow the OE community patch submission guidelines, as described in: 11For more details follow the OE community patch submission guidelines, as described in:
12 12
13https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines 13https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
14https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded 14https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
15 15
16`git send-email --subject-prefix 'meta-xilinx][PATCH' --to meta-xilinx@yoctoproject.org` 16`git send-email --to meta-xilinx@lists.yoctoproject.org *.patch`
17
18> **Note:** When creating patches, please use below format. To follow best practice,
19> if you have more than one patch use `--cover-letter` option while generating the
20> patches. Edit the 0000-cover-letter.patch and change the title and top of the
21> body as appropriate.
22
23**Syntax:**
24`git format-patch -s --subject-prefix="meta-xilinx][<BRANCH_NAME>][PATCH" -1`
25
26**Example:**
27`git format-patch -s --subject-prefix="meta-xilinx][langdale][PATCH" -1`
17 28
18**Maintainers:** 29**Maintainers:**
19 30