Re: [hwloc-devel] Stop updating Trac wiki (Github migration)

2014-09-09 Thread Jeff Squyres (jsquyres) 
Yoinks!

Autocomplete in my email client sent this to the wrong list... hwloc conversion 
is already done.  This message was meant for the main Open MPI developers list, 
not the hwloc list.

Sorry for the noise...


On Sep 9, 2014, at 12:03 PM, Jeff Squyres (jsquyres)  wrote:

> As part of our migration to Github, there are three main things to convert:
> 
> 1. SVN -> Git
> 2. Trac wiki -> Github markdown
> 3. Track tickets -> Github issues
> 
> I have a good automated solution for #1; that can be run whenever we're ready 
> to switchover.
> 
> I used an 80% automated solution for #2 (i.e., a bunch of regexps), and then 
> did a bunch of manual fixups for what the regexps didn't catch.  You can see 
> the result here (temporarily):
> 
>https://github.com/jsquyres/ompi-test/wiki
> 
> *** PLEASE DO NOT UPDATE THE TRAC WIKI ANY MORE!  The trac wiki page 
> conversion is basically done, and I don't intend to do it again.
> 
> Meaning: if you make any updates to the Trac wiki, they won't be brought over 
> to the new github wiki.
> 
> Lastly, I'm just starting to see about converting Trac tickets to Github 
> issues.  I'll be working on that this week, and hope to have updated 
> information for everyone for next Tuesday's call.
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/hwloc-devel/2014/09/4208.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

[hwloc-devel] Stop updating Trac wiki (Github migration)

2014-09-09 Thread Jeff Squyres (jsquyres) 
As part of our migration to Github, there are three main things to convert:

1. SVN -> Git
2. Trac wiki -> Github markdown
3. Track tickets -> Github issues

I have a good automated solution for #1; that can be run whenever we're ready 
to switchover.

I used an 80% automated solution for #2 (i.e., a bunch of regexps), and then 
did a bunch of manual fixups for what the regexps didn't catch.  You can see 
the result here (temporarily):

https://github.com/jsquyres/ompi-test/wiki

*** PLEASE DO NOT UPDATE THE TRAC WIKI ANY MORE!  The trac wiki page conversion 
is basically done, and I don't intend to do it again.

Meaning: if you make any updates to the Trac wiki, they won't be brought over 
to the new github wiki.

Lastly, I'm just starting to see about converting Trac tickets to Github 
issues.  I'll be working on that this week, and hope to have updated 
information for everyone for next Tuesday's call.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/