diff options
author | Tom Zanussi <tom.zanussi@linux.intel.com> | 2014-01-14 16:00:35 -0600 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2014-01-15 12:59:32 -0600 |
commit | 381f53495e662454873ff858e4d40a64e3b20a55 (patch) | |
tree | 4752ab41a48123f8ec1c33b5443b67cc25e09f4d /MAINTAINERS | |
parent | 7e1853808c8b325bfc6afa00265370c05f469e65 (diff) | |
download | meta-intel-381f53495e662454873ff858e4d40a64e3b20a55.tar.gz |
meta-intel: Clarify and relocate patch submission guidelines
The current location for patch submission guidelines, MAINTAINERS,
doesn't make as much sense for that information as does README, so
move the relevant information there.
The existing patch submission guidelines also aren't as clear and
exhaustive as they could be; this change additionally adds more
detailed expectations for patch submission.
Both files also get a bit of reorganization and a bit more explicit
text describing their purpose.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Diffstat (limited to 'MAINTAINERS')
-rw-r--r-- | MAINTAINERS | 31 |
1 files changed, 11 insertions, 20 deletions
diff --git a/MAINTAINERS b/MAINTAINERS index 10b2d377..0c868f22 100644 --- a/MAINTAINERS +++ b/MAINTAINERS | |||
@@ -1,26 +1,17 @@ | |||
1 | This file contains a list of BSP maintainers for the BSPs contained in | 1 | This file contains a list of BSP maintainers for the BSPs contained in |
2 | the meta-intel repository. | 2 | the meta-intel repository. |
3 | 3 | ||
4 | Please submit any patches against meta-intel BSPs to the meta-intel | 4 | The purpose of this file is to provide contact information for |
5 | mailing list (meta-intel@yoctoproject.org). Also, if your patches are | 5 | specific BSPs and other code contained within meta-intel. You should |
6 | available via a public git repository, please also include a URL to | 6 | address questions and patches for a particular BSP or other code to |
7 | the repo and branch containing your patches as that makes it easier | 7 | the appropriate maintainer listed in this file, cc'ing the meta-intel |
8 | for maintainers to grab and test your patches. | 8 | mailing list. This ensures that your question or patch will be |
9 | 9 | addressed by the appropriate person, and that it will be seen by other | |
10 | If you have problems with or questions about a particular BSP, feel | 10 | users who may be facing similar problems or questions. |
11 | free to contact the maintainer directly (cc:ing the Yocto mailing list | 11 | |
12 | puts it in the archive and helps other people who might have the same | 12 | Please see the top-level README file for guidelines relating to the |
13 | questions in the future), but please try to do the following first: | 13 | details of submitting patches, reporting problems, or asking questions |
14 | 14 | about any of the BSPs or other recipes contained within meta-intel. | |
15 | - look in the Yocto Project Bugzilla | ||
16 | (http://bugzilla.yoctoproject.org/) to see if a problem has | ||
17 | already been reported | ||
18 | |||
19 | - look through recent entries of the meta-intel | ||
20 | (https://lists.yoctoproject.org/pipermail/meta-intel/) and Yocto | ||
21 | (https://lists.yoctoproject.org/pipermail/yocto/) mailing list | ||
22 | archives to see if other people have run into similar problems or | ||
23 | had similar questions answered. | ||
24 | 15 | ||
25 | Descriptions of section entries: | 16 | Descriptions of section entries: |
26 | 17 | ||