All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com,
	meta-intel@yoctoproject.org
Subject: Re: [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info
Date: Sun, 11 Nov 2012 18:22:44 -0500	[thread overview]
Message-ID: <50A03344.5020005@balister.org> (raw)
In-Reply-To: <eafe70e873312e1b893408a8157501edcf0e6415.1352667964.git.tom.zanussi@intel.com>

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


  reply	other threads:[~2012-11-11 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 23:18 [PATCH 0/1] meta-intel: new meta-intel mailing list information tom.zanussi
2012-11-11 23:18 ` [PATCH 1/1] meta-intel: update MAINTAINERS with meta-intel mailing list info tom.zanussi
2012-11-11 23:22   ` Philip Balister [this message]
2012-11-11 23:27     ` Tom Zanussi
2012-11-12 23:27       ` Michael Halstead

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=50A03344.5020005@balister.org \
    --to=philip@balister.org \
    --cc=dvhart@linux.intel.com \
    --cc=meta-intel@yoctoproject.org \
    --cc=tom.zanussi@intel.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.