[PATCH 0/1] meta-intel: new meta-intel mailing list information

[PATCH 0/1] meta-intel: new meta-intel mailing list information

[tom.zanussi]

From: Tom Zanussi <tom.zanussi@intel.com>

There's a new mailing list for meta-intel traffic:

 https://lists.yoctoproject.org/listinfo/meta-intel

meta-intel patches and other meta-intel-specific e-mail should now
go there instead of to the Yocto mailing list.

This patchset updates the MAINTAINERS file with that info.

The following changes since commit 52a9a5aec7cc61d115e72015fd2451facec739cb:

  romley: Update README Instructions (2012-11-08 09:29:04 -0600)

are available in the git repository at:

  git://git.yoctoproject.org/meta-intel-contrib.git tzanussi/meta-intel-mailing-list-update
  http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi/meta-intel-mailing-list-update

Tom Zanussi (1):
  meta-intel: update MAINTAINERS with meta-intel mailing list info

 MAINTAINERS | 32 ++++++++++++++++++--------------
 1 file changed, 18 insertions(+), 14 deletions(-)

-- 
1.7.11.4

[PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info

[tom.zanussi]

From: Tom Zanussi <tom.zanussi@intel.com>

The newly created meta-intel mailing list is where meta-intel-specific
e-mail and patches should now go.  Update MAINTAINERS with that
information.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
---
 MAINTAINERS | 32 ++++++++++++++++++--------------
 1 file changed, 18 insertions(+), 14 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a2231d0..d5f521b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,26 +1,30 @@
 This file contains a list of BSP maintainers for the BSPs contained in
 the meta-intel repository.
 
-Please submit any patches against meta-intel BSPs to the Yocto mailing
-list (yocto@yoctoproject.org) and preface them with [meta-intel] in
-the Subject: line of your e-mail(s).  The latter makes it obvious that
-your patches are intended for inclusion into meta-intel and also makes
-it easier for maintainers to notice patches intended for meta-intel
-amongst all the other traffic on the Yocto mailing list.  Also, if
-your patches are available via a public git repository, please also
-include a URL to the repo and branch containing your patches as that
-makes it easier for maintainers to grab and test your patches.
+Please submit any patches against meta-intel BSPs to the meta-intel
+mailing list (meta-intel@yoctoproject.org).  Also, if your patches are
+available via a public git repository, please include a URL to the
+repo and branch containing your patches as that makes it easier for
+maintainers to grab and test your patches.
+
+The web page for users of the meta-intel mailing list is
+https://lists.yoctoproject.org/listinfo/meta-intel, where you can
+subscribe to the list (please do, especially if you intend on
+submitting patches).
 
 If you have problems with or questions about a particular BSP, feel
-free to contact the maintainer directly (cc:ing the Yocto mailing list
-puts it in the archive and helps other people who might have the same
-questions in the future), but please try to do the following first:
+free to contact the maintainer directly (cc:ing the meta-intel mailing
+list puts it in the archive and helps other people who might have the
+same questions in the future), but please try to do the following
+first:
 
   - look in the Yocto Project Bugzilla
     (http://bugzilla.yoctoproject.org/) to see if a problem has
-    already been reported
+    already been reported.
 
-  - look through recent entries of the Yocto mailing list archives
+  - look through recent entries of the meta-intel mailing list
+    archives (https://lists.yoctoproject.org/pipermail/meta-intel/)
+    and the Yocto mailing list archives
     (https://lists.yoctoproject.org/pipermail/yocto/) to see if other
     people have run into similar problems or had similar questions
     answered.
-- 
1.7.11.4

Re: [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info

[Philip Balister]

On 11/11/2012 06:18 PM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> The newly created meta-intel mailing list is where meta-intel-specific
> e-mail and patches should now go.  Update MAINTAINERS with that
> information.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
>   MAINTAINERS | 32 ++++++++++++++++++--------------
>   1 file changed, 18 insertions(+), 14 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a2231d0..d5f521b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1,26 +1,30 @@
>   This file contains a list of BSP maintainers for the BSPs contained in
>   the meta-intel repository.
>
> -Please submit any patches against meta-intel BSPs to the Yocto mailing
> -list (yocto@yoctoproject.org) and preface them with [meta-intel] in
> -the Subject: line of your e-mail(s).  The latter makes it obvious that
> -your patches are intended for inclusion into meta-intel and also makes
> -it easier for maintainers to notice patches intended for meta-intel
> -amongst all the other traffic on the Yocto mailing list.  Also, if
> -your patches are available via a public git repository, please also
> -include a URL to the repo and branch containing your patches as that
> -makes it easier for maintainers to grab and test your patches.
> +Please submit any patches against meta-intel BSPs to the meta-intel
> +mailing list (meta-intel@yoctoproject.org).  Also, if your patches are
> +available via a public git repository, please include a URL to the
> +repo and branch containing your patches as that makes it easier for
> +maintainers to grab and test your patches.
> +
> +The web page for users of the meta-intel mailing list is
> +https://lists.yoctoproject.org/listinfo/meta-intel, where you can
> +subscribe to the list (please do, especially if you intend on
> +submitting patches).
>
>   If you have problems with or questions about a particular BSP, feel
> -free to contact the maintainer directly (cc:ing the Yocto mailing list
> -puts it in the archive and helps other people who might have the same
> -questions in the future), but please try to do the following first:
> +free to contact the maintainer directly (cc:ing the meta-intel mailing
> +list puts it in the archive and helps other people who might have the
> +same questions in the future), but please try to do the following
> +first:
>
>     - look in the Yocto Project Bugzilla
>       (http://bugzilla.yoctoproject.org/) to see if a problem has
> -    already been reported
> +    already been reported.
>
> -  - look through recent entries of the Yocto mailing list archives
> +  - look through recent entries of the meta-intel mailing list
> +    archives (https://lists.yoctoproject.org/pipermail/meta-intel/)
> +    and the Yocto mailing list archives
>       (https://lists.yoctoproject.org/pipermail/yocto/) to see if other
>       people have run into similar problems or had similar questions
>       answered.
>

Can you setup gmane to archive the list also? Then people can follow the 
list using NNTP.

Philip

Re: [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info

[Tom Zanussi]

On Sun, 2012-11-11 at 18:22 -0500, Philip Balister wrote:
> On 11/11/2012 06:18 PM, tom.zanussi@intel.com wrote:
> > From: Tom Zanussi <tom.zanussi@intel.com>
> >
> > The newly created meta-intel mailing list is where meta-intel-specific
> > e-mail and patches should now go.  Update MAINTAINERS with that
> > information.
> >
> > Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> > ---
> >   MAINTAINERS | 32 ++++++++++++++++++--------------
> >   1 file changed, 18 insertions(+), 14 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index a2231d0..d5f521b 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1,26 +1,30 @@
> >   This file contains a list of BSP maintainers for the BSPs contained in
> >   the meta-intel repository.
> >
> > -Please submit any patches against meta-intel BSPs to the Yocto mailing
> > -list (yocto@yoctoproject.org) and preface them with [meta-intel] in
> > -the Subject: line of your e-mail(s).  The latter makes it obvious that
> > -your patches are intended for inclusion into meta-intel and also makes
> > -it easier for maintainers to notice patches intended for meta-intel
> > -amongst all the other traffic on the Yocto mailing list.  Also, if
> > -your patches are available via a public git repository, please also
> > -include a URL to the repo and branch containing your patches as that
> > -makes it easier for maintainers to grab and test your patches.
> > +Please submit any patches against meta-intel BSPs to the meta-intel
> > +mailing list (meta-intel@yoctoproject.org).  Also, if your patches are
> > +available via a public git repository, please include a URL to the
> > +repo and branch containing your patches as that makes it easier for
> > +maintainers to grab and test your patches.
> > +
> > +The web page for users of the meta-intel mailing list is
> > +https://lists.yoctoproject.org/listinfo/meta-intel, where you can
> > +subscribe to the list (please do, especially if you intend on
> > +submitting patches).
> >
> >   If you have problems with or questions about a particular BSP, feel
> > -free to contact the maintainer directly (cc:ing the Yocto mailing list
> > -puts it in the archive and helps other people who might have the same
> > -questions in the future), but please try to do the following first:
> > +free to contact the maintainer directly (cc:ing the meta-intel mailing
> > +list puts it in the archive and helps other people who might have the
> > +same questions in the future), but please try to do the following
> > +first:
> >
> >     - look in the Yocto Project Bugzilla
> >       (http://bugzilla.yoctoproject.org/) to see if a problem has
> > -    already been reported
> > +    already been reported.
> >
> > -  - look through recent entries of the Yocto mailing list archives
> > +  - look through recent entries of the meta-intel mailing list
> > +    archives (https://lists.yoctoproject.org/pipermail/meta-intel/)
> > +    and the Yocto mailing list archives
> >       (https://lists.yoctoproject.org/pipermail/yocto/) to see if other
> >       people have run into similar problems or had similar questions
> >       answered.
> >
> 
> Can you setup gmane to archive the list also? Then people can follow the 
> list using NNTP.
> 

Sounds like a good idea to me, but I'll have to defer to Michael (added
to CC:

Tom

> Philip

Re: [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info

[Michael Halstead]

[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]

On 11/11/2012 03:27 PM, Tom Zanussi wrote:
> On Sun, 2012-11-11 at 18:22 -0500, Philip Balister wrote:
>> On 11/11/2012 06:18 PM, tom.zanussi@intel.com wrote:
>>> From: Tom Zanussi <tom.zanussi@intel.com>
>>>
>>> The newly created meta-intel mailing list is where meta-intel-specific
>>> e-mail and patches should now go.  Update MAINTAINERS with that
>>> information.
>>>
>>> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
>>> ---
>>>   MAINTAINERS | 32 ++++++++++++++++++--------------
>>>   1 file changed, 18 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index a2231d0..d5f521b 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -1,26 +1,30 @@
>>>   This file contains a list of BSP maintainers for the BSPs contained in
>>>   the meta-intel repository.
>>>
>>> -Please submit any patches against meta-intel BSPs to the Yocto mailing
>>> -list (yocto@yoctoproject.org) and preface them with [meta-intel] in
>>> -the Subject: line of your e-mail(s).  The latter makes it obvious that
>>> -your patches are intended for inclusion into meta-intel and also makes
>>> -it easier for maintainers to notice patches intended for meta-intel
>>> -amongst all the other traffic on the Yocto mailing list.  Also, if
>>> -your patches are available via a public git repository, please also
>>> -include a URL to the repo and branch containing your patches as that
>>> -makes it easier for maintainers to grab and test your patches.
>>> +Please submit any patches against meta-intel BSPs to the meta-intel
>>> +mailing list (meta-intel@yoctoproject.org).  Also, if your patches are
>>> +available via a public git repository, please include a URL to the
>>> +repo and branch containing your patches as that makes it easier for
>>> +maintainers to grab and test your patches.
>>> +
>>> +The web page for users of the meta-intel mailing list is
>>> +https://lists.yoctoproject.org/listinfo/meta-intel, where you can
>>> +subscribe to the list (please do, especially if you intend on
>>> +submitting patches).
>>>
>>>   If you have problems with or questions about a particular BSP, feel
>>> -free to contact the maintainer directly (cc:ing the Yocto mailing list
>>> -puts it in the archive and helps other people who might have the same
>>> -questions in the future), but please try to do the following first:
>>> +free to contact the maintainer directly (cc:ing the meta-intel mailing
>>> +list puts it in the archive and helps other people who might have the
>>> +same questions in the future), but please try to do the following
>>> +first:
>>>
>>>     - look in the Yocto Project Bugzilla
>>>       (http://bugzilla.yoctoproject.org/) to see if a problem has
>>> -    already been reported
>>> +    already been reported.
>>>
>>> -  - look through recent entries of the Yocto mailing list archives
>>> +  - look through recent entries of the meta-intel mailing list
>>> +    archives (https://lists.yoctoproject.org/pipermail/meta-intel/)
>>> +    and the Yocto mailing list archives
>>>       (https://lists.yoctoproject.org/pipermail/yocto/) to see if other
>>>       people have run into similar problems or had similar questions
>>>       answered.
>>>
>> Can you setup gmane to archive the list also? Then people can follow the 
>> list using NNTP.
I've requested this list be added to Gmane. It should be picked up shortly.

Michael Halstead
Yocto Project / Sys Admin

> Sounds like a good idea to me, but I'll have to defer to Michael (added
> to CC:
>
> Tom
>
>> Philip
>
>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4516 bytes --]