All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Birin Sanchez <birin.sanchez@citrix.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
	Thomas Leonard <talex5@gmail.com>,
	xen-devel@lists.xensource.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: Mini-os mailing list
Date: Mon, 18 May 2015 13:54:45 +0100	[thread overview]
Message-ID: <21849.57621.648871.520005@mariner.uk.xensource.com> (raw)
In-Reply-To: <1431333174.2660.554.camel@citrix.com>

Birin, would you please create the list requested below ?

Thanks,
Ian.

Ian Campbell writes ("Re: [Xen-devel] Mini-os mailing list"):
> (Sending this to IanJ's inbox)
> 
> On Wed, 2015-05-06 at 18:47 +0100, Thomas Leonard wrote:
> > On 01/29/2015 05:04 PM, George Dunlap wrote:
> > > On Tue, Jan 27, 2015 at 6:49 AM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> > >> We are splitting minios out of xen.git (because we want to try to make
> > >> it easier to un-fork it - there are about 3-4 forks that we are aware
> > >> of).
> > >>
> > >> We think it should have its own mailing list.  I propose
> > >> "minios-devel@lists.xenproject.org".
> > >>
> > >> Existing subscribers to xen-devel should continue to get the minios
> > >> traffic.  This is probably best done by having the initial subscriber
> > >> list be populated from the subscribers to xen-devel.
> > >>
> > >> Is there any objection to me just doing this ?
> > > 
> > > Not from me.
> > > 
> > >  -George
> > 
> > Did this ever happen? Having a separate list would be very useful.

  reply	other threads:[~2015-05-18 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 11:49 Mini-os mailing list Ian Jackson
2015-01-29 17:04 ` George Dunlap
2015-05-06 17:47   ` Thomas Leonard
2015-05-11  8:32     ` Ian Campbell
2015-05-18 12:54       ` Ian Jackson [this message]
2015-05-31 10:55         ` Thomas Leonard

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=21849.57621.648871.520005@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=birin.sanchez@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=talex5@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.