Ok, I heard no further feedback, either in email or on the webex today, so I'm
assuming that this list is final. More detail coming shortly.
> On Jul 18, 2016, at 9:55 PM, Jeff Squyres (jsquyres)
> wrote:
>
> On Jul 18, 2016, at 9:46 PM, Christopher Samuel wrote:
>>
>>> Yes, kill all netlo
On Jul 18, 2016, at 9:46 PM, Christopher Samuel wrote:
>
>> Yes, kill all netloc lists.
>
> Will the archives be preserved somewhere for historical reference?
The plan is to preserve the list archives as they exist right now, even if we
don't migrate the list.
--
Jeff Squyres
jsquy...@cisco.
On 19/07/16 02:05, Brice Goglin wrote:
> Yes, kill all netloc lists.
Will the archives be preserved somewhere for historical reference?
All the best,
Chris
--
Christopher SamuelSenior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
Email: sam...@unimelb.e
Roger.
> On Jul 18, 2016, at 12:05 PM, Brice Goglin wrote:
>
> Yes, kill all netloc lists.
> Brice
>
>
> Le 18 juillet 2016 17:43:49 UTC+02:00, Josh Hursey a
> écrit :
> Now that netloc has rolled into hwloc, I think it is safe to kill the netloc
> lists.
>
> mtt-devel-core and mtt-annouce
Yes, kill all netloc lists.
Brice
Le 18 juillet 2016 17:43:49 UTC+02:00, Josh Hursey a
écrit :
>Now that netloc has rolled into hwloc, I think it is safe to kill the
>netloc lists.
>
>mtt-devel-core and mtt-annouce should be kept. They probably need to be
>cleaned. But the hope is that we relea
Now that netloc has rolled into hwloc, I think it is safe to kill the
netloc lists.
mtt-devel-core and mtt-annouce should be kept. They probably need to be
cleaned. But the hope is that we release MTT at some point in the near-ish
future.
On Mon, Jul 18, 2016 at 10:20 AM, Jeff Squyres (jsquyres)
We're progressing in the migration plans. Next up is the mailing lists. The
first step is to determine which lists to migrate, and which to delete (because
they're now no longer necessary, anyway).
These are the lists we plan to keep/migrate, and the lists we plan to
delete/not migrate -- if
