[OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

(sorry for the delay in receiving this mail; there was a problem with the devel 
mailing list last night, unrelated to the Github migration)

Short version
=

The Github conversion is complete.  All OMPI activity is now at Github.  Please 
read the wiki, particularly the first few pages that deal specifically with 
Git/Github:

https://github.com/open-mpi/ompi/wiki

You can safely re-enable your "watch" settings on our main repos now:

https://github.com/open-mpi/ompi
https://github.com/open-mpi/ompi-release

"make dist" and nightly tarballs are not quite functional yet; I am getting 
tangled up in version numbering, and did not finish it last night.  But 
everything else seems to be working.

Several people need to file pull requests to replace their still-open CMRs that 
were orphaned at Trac.

A few people need to accept their Github "ompi" invitations so that Github 
Issues can be assigned to them: 

More detail
===

1. The following people need to accept the OMPI GitHub invite email so that 
issues can be assigned to them:

- Manjunath Gorentla Venkata
- Vasily Philipov

Please tell me when you've accepted so that I can assign the proper issue(s) to 
you.

2. The following still-open CMRs were not brought over, and need to be re-filed 
as pull requests:

- https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
- https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
- https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
- https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
- https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
- https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff

3. As mentioned above, you can safely start watching the ompi and ompi-release 
repos again.  You can pick either:

3a. "Watching", which means you'll get an email for every issue/pull request, or
3b. "Not watching", which means you'll only get an email if someone @mentions 
you, or an issue is assigned to you.

*** If you want to receive emails for every issue filed, you want "Watching".  
The old "bugs" email list does not exist any longer.
*** You almost certainly *don't* want "Ignoring", which means you won't ever 
get emails, even if someone @mentions or, or an issue is assigned to you.

4. If you hadn't noticed already, mails about commits to the following repos 
are now sent to the ompi-comm...@open-mpi.org mailman list:

4a. ompi
4b. ompi-release
4c. ompi-tests
4d. ompi-www
4e. ompi-docs

The "svn" and "svn-full" mailman lists no longer exist.  If we want to split up 
where the commits go to be more fine-grained than that, we can.

5. As mentioned above, "make dist" and friends is currently broken.  Don't 
bother trying it; I'm partway through fixing it, but it's subtle and 
complicated, and I'm was too brain fried last night to finish it correctly.  
More fixing in this area coming soon...

6. After you read the wiki about git/GitHub usage 
(https://github.com/open-mpi/ompi/wiki), please let me know if you run into any 
problems (unrelated to "make dist" and version numbers) and/or have any 
questions.

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Gilles Gouaillardet]

Hi Jeff,

thumbs up for the migration !

the names here are the CMR owners ('Owned by' field in TRAC)
should it be the duty of the creators ('Reported by' field in TRAC) to
re-create the CMR instead?

/* if not, and from a git log point of view, that means the commiter
will be the reviewer and not the reporter */

what do you think ?

Cheers,

Gilles

On 2014/10/02 19:24, Jeff Squyres (jsquyres) wrote:
> 2. The following still-open CMRs were not brought over, and need to be 
> re-filed as pull requests:
>
> - https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
> - https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
> - https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
> - https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
> - https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
> - https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
> - https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
> - https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
> - https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
> - https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
> - https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
> - https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
> - https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

Fair enough.

*Someone* needs to re-file those CMRs as pull requests; probably in some cases 
it's the reporter, probably in some cases it's the owner.  :-)


On Oct 2, 2014, at 6:33 AM, Gilles Gouaillardet  
wrote:

> Hi Jeff,
> 
> thumbs up for the migration !
> 
> the names here are the CMR owners ('Owned by' field in TRAC)
> should it be the duty of the creators ('Reported by' field in TRAC) to
> re-create the CMR instead?
> 
> /* if not, and from a git log point of view, that means the commiter
> will be the reviewer and not the reporter */
> 
> what do you think ?
> 
> Cheers,
> 
> Gilles
> 
> On 2014/10/02 19:24, Jeff Squyres (jsquyres) wrote:
>> 2. The following still-open CMRs were not brought over, and need to be 
>> re-filed as pull requests:
>> 
>> - https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
>> - https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
>> - https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
>> - https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
>> - https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
>> - https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
>> - https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
>> - https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
>> - https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
>> - https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
>> - https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
>> - https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
>> - https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15966.php


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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Vasily Filipov]

Hi Jeff,
I didn't get any "OMPI GitHub invite email ", I opened GitHub account 
(vasilyMellanox) and set a "Watch" state for :


https://github.com/open-mpi/ompi
https://github.com/open-mpi/ompi-release

Am I supposed to do something additional ?

Thank you,
Vasily.

On 02-Oct-14 13:24, Jeff Squyres (jsquyres) wrote:

(sorry for the delay in receiving this mail; there was a problem with the devel 
mailing list last night, unrelated to the Github migration)

Short version
=

The Github conversion is complete.  All OMPI activity is now at Github.  Please 
read the wiki, particularly the first few pages that deal specifically with 
Git/Github:

 https://github.com/open-mpi/ompi/wiki

You can safely re-enable your "watch" settings on our main repos now:

 https://github.com/open-mpi/ompi
 https://github.com/open-mpi/ompi-release

"make dist" and nightly tarballs are not quite functional yet; I am getting 
tangled up in version numbering, and did not finish it last night.  But everything else 
seems to be working.

Several people need to file pull requests to replace their still-open CMRs that 
were orphaned at Trac.

A few people need to accept their Github "ompi" invitations so that Github 
Issues can be assigned to them:

More detail
===

1. The following people need to accept the OMPI GitHub invite email so that 
issues can be assigned to them:

- Manjunath Gorentla Venkata
- Vasily Philipov

Please tell me when you've accepted so that I can assign the proper issue(s) to 
you.

2. The following still-open CMRs were not brought over, and need to be re-filed 
as pull requests:

- https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
- https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
- https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
- https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
- https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
- https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff

3. As mentioned above, you can safely start watching the ompi and ompi-release 
repos again.  You can pick either:

3a. "Watching", which means you'll get an email for every issue/pull request, or
3b. "Not watching", which means you'll only get an email if someone @mentions 
you, or an issue is assigned to you.

*** If you want to receive emails for every issue filed, you want "Watching".  The old 
"bugs" email list does not exist any longer.
*** You almost certainly *don't* want "Ignoring", which means you won't ever 
get emails, even if someone @mentions or, or an issue is assigned to you.

4. If you hadn't noticed already, mails about commits to the following repos 
are now sent to the ompi-comm...@open-mpi.org mailman list:

4a. ompi
4b. ompi-release
4c. ompi-tests
4d. ompi-www
4e. ompi-docs

The "svn" and "svn-full" mailman lists no longer exist.  If we want to split up 
where the commits go to be more fine-grained than that, we can.

5. As mentioned above, "make dist" and friends is currently broken.  Don't 
bother trying it; I'm partway through fixing it, but it's subtle and complicated, and I'm 
was too brain fried last night to finish it correctly.  More fixing in this area coming 
soon...

6. After you read the wiki about git/GitHub usage 
(https://github.com/open-mpi/ompi/wiki), please let me know if you run into any problems 
(unrelated to "make dist" and version numbers) and/or have any questions.

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

According to Github, you haven't accepted your invitation yet:

[cid:34B7E99E-FBB8-4B2D-974A-6FAF2CC15E82@cisco.com]


On Oct 2, 2014, at 9:35 AM, Vasily Filipov 
mailto:vas...@dev.mellanox.co.il>> wrote:

Hi Jeff,
I didn't get any "OMPI GitHub invite email ", I opened GitHub account 
(vasilyMellanox) and set a "Watch" state for :

   https://github.com/open-mpi/ompi
   https://github.com/open-mpi/ompi-release

Am I supposed to do something additional ?

Thank you,
Vasily.

On 02-Oct-14 13:24, Jeff Squyres (jsquyres) wrote:
(sorry for the delay in receiving this mail; there was a problem with the devel 
mailing list last night, unrelated to the Github migration)

Short version
=

The Github conversion is complete.  All OMPI activity is now at Github.  Please 
read the wiki, particularly the first few pages that deal specifically with 
Git/Github:

https://github.com/open-mpi/ompi/wiki

You can safely re-enable your "watch" settings on our main repos now:

https://github.com/open-mpi/ompi
https://github.com/open-mpi/ompi-release

"make dist" and nightly tarballs are not quite functional yet; I am getting 
tangled up in version numbering, and did not finish it last night.  But 
everything else seems to be working.

Several people need to file pull requests to replace their still-open CMRs that 
were orphaned at Trac.

A few people need to accept their Github "ompi" invitations so that Github 
Issues can be assigned to them:

More detail
===

1. The following people need to accept the OMPI GitHub invite email so that 
issues can be assigned to them:

- Manjunath Gorentla Venkata
- Vasily Philipov

Please tell me when you've accepted so that I can assign the proper issue(s) to 
you.

2. The following still-open CMRs were not brought over, and need to be re-filed 
as pull requests:

- https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
- https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
- https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
- https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
- https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
- https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
- https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
- https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff

3. As mentioned above, you can safely start watching the ompi and ompi-release 
repos again.  You can pick either:

3a. "Watching", which means you'll get an email for every issue/pull request, or
3b. "Not watching", which means you'll only get an email if someone @mentions 
you, or an issue is assigned to you.

*** If you want to receive emails for every issue filed, you want "Watching".  
The old "bugs" email list does not exist any longer.
*** You almost certainly *don't* want "Ignoring", which means you won't ever 
get emails, even if someone @mentions or, or an issue is assigned to you.

4. If you hadn't noticed already, mails about commits to the following repos 
are now sent to the ompi-comm...@open-mpi.org 
mailman list:

4a. ompi
4b. ompi-release
4c. ompi-tests
4d. ompi-www
4e. ompi-docs

The "svn" and "svn-full" mailman lists no longer exist.  If we want to split up 
where the commits go to be more fine-grained than that, we can.

5. As mentioned above, "make dist" and friends is currently broken.  Don't 
bother trying it; I'm partway through fixing it, but it's subtle and 
complicated, and I'm was too brain fried last night to finish it correctly.  
More fixing in this area coming soon...

6. After you read the wiki about git/GitHub usage 
(https://github.com/open-mpi/ompi/wiki), please let me know if you run into any 
problems (unrelated to "make dist" and version numbers) and/or have any 
questions.


___
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post: 
http://www.open-mpi.org/community/lists/devel/2014/10/15968.php


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

[OMPI devel] End of life: Bitbucket and Github read-only SVN mirrors

[Jeff Squyres (jsquyres)]

Now that Open has migrated its repositories to GitHub, there is no point in 
maintaining the read-only Bitbucket and GitHub mirrors of OMPI's SVN repository 
any further.  They are, respectively:

https://bitbucket.org/ompiteam/ompi-svn-mirror
https://github.com/open-mpi/ompi-svn-mirror

Unless someone has a dire need to keep these mirrors existent for some reason 
(I can't think of a good reason offhand?), I plan to delete them next Friday, 
10 Oct, 2014.

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

I agree that someone needs to do it. However, what isn't clear is *how* to do 
it. I get the mechanics:

* clone the ompi-release 1.8 branch
* apply the required change
* issue a pull request

It's the second step that isn't clear. How the heck do I (a) find the change 
that was originally applied, and (b) apply it to my clone of ompi-release???

Do I just download the changeset(s) from Trac and patch them in? I guess that 
will work if we don't have an alternative method.


On Oct 2, 2014, at 3:41 AM, Jeff Squyres (jsquyres)  wrote:

> Fair enough.
> 
> *Someone* needs to re-file those CMRs as pull requests; probably in some 
> cases it's the reporter, probably in some cases it's the owner.  :-)
> 
> 
> On Oct 2, 2014, at 6:33 AM, Gilles Gouaillardet 
>  wrote:
> 
>> Hi Jeff,
>> 
>> thumbs up for the migration !
>> 
>> the names here are the CMR owners ('Owned by' field in TRAC)
>> should it be the duty of the creators ('Reported by' field in TRAC) to
>> re-create the CMR instead?
>> 
>> /* if not, and from a git log point of view, that means the commiter
>> will be the reviewer and not the reporter */
>> 
>> what do you think ?
>> 
>> Cheers,
>> 
>> Gilles
>> 
>> On 2014/10/02 19:24, Jeff Squyres (jsquyres) wrote:
>>> 2. The following still-open CMRs were not brought over, and need to be 
>>> re-filed as pull requests:
>>> 
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
>>> - https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff
>> 
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/10/15966.php
> 
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15967.php

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-9-g3263f72

[Dave Goodell (dgoodell)]

On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:

> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "open-mpi/ompi".
> 
> The branch, master has been updated
>   via  3263f721b6a21966a1c1eea0fdac2a558a15db06 (commit)
>  from  f21c349bcb3f7c322805d505484951642d1c7965 (commit)
> 
> Those revisions listed above that are new to this repository have
> not appeared on any other notification email; so we list those
> revisions in full, below.
> 
> - Log -
> https://github.com/open-mpi/ompi/commit/3263f721b6a21966a1c1eea0fdac2a558a15db06
> 
> commit 3263f721b6a21966a1c1eea0fdac2a558a15db06
> Author: Ralph Castain 
> Date:   Thu Oct 2 08:37:18 2014 -0700
> 
>Strip crlf line endings
> 
> diff --git a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln 
> b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
> index 38498d6..7e887fc 100644
> --- a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
> +++ b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln

Isn't this file a Windows-specific file that probably should still have CRLF 
line endings?

-Dave

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

On Oct 2, 2014, at 11:51 AM, Ralph Castain  wrote:

> Do I just download the changeset(s) from Trac and patch them in? I guess that 
> will work if we don't have an alternative method.

Yes, that's what I was planning to do for my CMRs (i.e., generate patches from 
SVN and apply them git tree).

Per Gilles observation, I think https://svn.open-mpi.org/trac/ompi/ticket/4917 
is the only one that's actually mine (i.e., I need to create a PR for it).

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

On Oct 2, 2014, at 9:14 AM, Jeff Squyres (jsquyres)  wrote:

> On Oct 2, 2014, at 11:51 AM, Ralph Castain  wrote:
> 
>> Do I just download the changeset(s) from Trac and patch them in? I guess 
>> that will work if we don't have an alternative method.
> 
> Yes, that's what I was planning to do for my CMRs (i.e., generate patches 
> from SVN and apply them git tree).

FWIW: I've been trying that and it really, really doesn't work very well - at 
least, not on the one I'm trying to do. People should expect this to be 
extremely painful for the transition.


> 
> Per Gilles observation, I think 
> https://svn.open-mpi.org/trac/ompi/ticket/4917 is the only one that's 
> actually mine (i.e., I need to create a PR for it).
> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15973.php

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-9-g3263f72

[Ralph Castain]

On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell)  wrote:

> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
> 
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because a ref change was pushed to the repository containing
>> the project "open-mpi/ompi".
>> 
>> The branch, master has been updated
>>  via  3263f721b6a21966a1c1eea0fdac2a558a15db06 (commit)
>> from  f21c349bcb3f7c322805d505484951642d1c7965 (commit)
>> 
>> Those revisions listed above that are new to this repository have
>> not appeared on any other notification email; so we list those
>> revisions in full, below.
>> 
>> - Log -
>> https://github.com/open-mpi/ompi/commit/3263f721b6a21966a1c1eea0fdac2a558a15db06
>> 
>> commit 3263f721b6a21966a1c1eea0fdac2a558a15db06
>> Author: Ralph Castain 
>> Date:   Thu Oct 2 08:37:18 2014 -0700
>> 
>>   Strip crlf line endings
>> 
>> diff --git a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln 
>> b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>> index 38498d6..7e887fc 100644
>> --- a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>> +++ b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
> 
> Isn't this file a Windows-specific file that probably should still have CRLF 
> line endings?

No idea, but we don't support Windows any more, so who cares?

> 
> -Dave
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15972.php

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-9-g3263f72

[Dave Goodell (dgoodell)]

On Oct 2, 2014, at 11:17 AM, Ralph Castain 
 wrote:

> 
> On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell)  
> wrote:
> 
>> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
>> 
>>> This is an automated email from the git hooks/post-receive script. It was
>>> generated because a ref change was pushed to the repository containing
>>> the project "open-mpi/ompi".
>>> 
>>> The branch, master has been updated
>>>  via  3263f721b6a21966a1c1eea0fdac2a558a15db06 (commit)
>>> from  f21c349bcb3f7c322805d505484951642d1c7965 (commit)
>>> 
>>> Those revisions listed above that are new to this repository have
>>> not appeared on any other notification email; so we list those
>>> revisions in full, below.
>>> 
>>> - Log -
>>> https://github.com/open-mpi/ompi/commit/3263f721b6a21966a1c1eea0fdac2a558a15db06
>>> 
>>> commit 3263f721b6a21966a1c1eea0fdac2a558a15db06
>>> Author: Ralph Castain 
>>> Date:   Thu Oct 2 08:37:18 2014 -0700
>>> 
>>>   Strip crlf line endings
>>> 
>>> diff --git a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln 
>>> b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>>> index 38498d6..7e887fc 100644
>>> --- a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>>> +++ b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>> 
>> Isn't this file a Windows-specific file that probably should still have CRLF 
>> line endings?
> 
> No idea, but we don't support Windows any more, so who cares?

Right, but when the VT folks slurp in a new update from their upstream, won't 
this just get clobbered back to CRLF?  Or worse, cause some sort of merge 
conflict for them?

I don't especially care, just thought it was odd to remove the CRLFs from a 
Windows-only file.

-Dave

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

On Oct 2, 2014, at 12:16 PM, Ralph Castain  wrote:

> FWIW: I've been trying that and it really, really doesn't work very well - at 
> least, not on the one I'm trying to do. People should expect this to be 
> extremely painful for the transition.

Yes, I think people will have to be watch out for the fact that applying 
patches won't automatically git add/move/remove files for you.

Is that the big difficulty you're running in to?

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

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-9-g3263f72

[Ralph Castain]

On Oct 2, 2014, at 9:20 AM, Dave Goodell (dgoodell)  wrote:

> On Oct 2, 2014, at 11:17 AM, Ralph Castain 
> wrote:
> 
>> 
>> On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell)  
>> wrote:
>> 
>>> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
>>> 
 This is an automated email from the git hooks/post-receive script. It was
 generated because a ref change was pushed to the repository containing
 the project "open-mpi/ompi".
 
 The branch, master has been updated
 via  3263f721b6a21966a1c1eea0fdac2a558a15db06 (commit)
from  f21c349bcb3f7c322805d505484951642d1c7965 (commit)
 
 Those revisions listed above that are new to this repository have
 not appeared on any other notification email; so we list those
 revisions in full, below.
 
 - Log -
 https://github.com/open-mpi/ompi/commit/3263f721b6a21966a1c1eea0fdac2a558a15db06
 
 commit 3263f721b6a21966a1c1eea0fdac2a558a15db06
 Author: Ralph Castain 
 Date:   Thu Oct 2 08:37:18 2014 -0700
 
  Strip crlf line endings
 
 diff --git a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln 
 b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
 index 38498d6..7e887fc 100644
 --- a/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
 +++ b/ompi/contrib/vt/vt/extlib/otf/otf_vc08.sln
>>> 
>>> Isn't this file a Windows-specific file that probably should still have 
>>> CRLF line endings?
>> 
>> No idea, but we don't support Windows any more, so who cares?
> 
> Right, but when the VT folks slurp in a new update from their upstream, won't 
> this just get clobbered back to CRLF?  Or worse, cause some sort of merge 
> conflict for them?

Yes - and it'll get reset again on the next git checkin/out so we keep crlf's 
out

> 
> I don't especially care, just thought it was odd to remove the CRLFs from a 
> Windows-only file.
> 
> -Dave
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15976.php

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

On Oct 2, 2014, at 9:21 AM, Jeff Squyres (jsquyres)  wrote:

> On Oct 2, 2014, at 12:16 PM, Ralph Castain  wrote:
> 
>> FWIW: I've been trying that and it really, really doesn't work very well - 
>> at least, not on the one I'm trying to do. People should expect this to be 
>> extremely painful for the transition.
> 
> Yes, I think people will have to be watch out for the fact that applying 
> patches won't automatically git add/move/remove files for you.
> 
> Is that the big difficulty you're running in to?

No. Getting all the right patches (one at a time) from svn is slow, and 
then it doesn't necessarily apply cleanly, so you go back to svn to figure out 
what is missing, get another set of patches (one at a time), try again from 
scratch, etc. etc.

Probably going to drop some of these CMRs as just too painful

> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15977.php

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

Sonow that I've fought thru and created a pull request, I find that I 
cannot assign it to anyone for review. The only users on the ompi-release 
branch are myself and Jeff (plus the ompiteam admin).

So how do we assign someone to review it?


On Oct 2, 2014, at 9:25 AM, Ralph Castain  wrote:

> 
> On Oct 2, 2014, at 9:21 AM, Jeff Squyres (jsquyres)  
> wrote:
> 
>> On Oct 2, 2014, at 12:16 PM, Ralph Castain  wrote:
>> 
>>> FWIW: I've been trying that and it really, really doesn't work very well - 
>>> at least, not on the one I'm trying to do. People should expect this to be 
>>> extremely painful for the transition.
>> 
>> Yes, I think people will have to be watch out for the fact that applying 
>> patches won't automatically git add/move/remove files for you.
>> 
>> Is that the big difficulty you're running in to?
> 
> No. Getting all the right patches (one at a time) from svn is slow, 
> and then it doesn't necessarily apply cleanly, so you go back to svn to 
> figure out what is missing, get another set of patches (one at a time), try 
> again from scratch, etc. etc.
> 
> Probably going to drop some of these CMRs as just too painful
> 
>> 
>> -- 
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to: 
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>> 
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/10/15977.php
> 

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

On Oct 2, 2014, at 12:25 PM, Ralph Castain  wrote:

> No. Getting all the right patches (one at a time) from svn is slow, 
> and then it doesn't necessarily apply cleanly, so you go back to svn to 
> figure out what is missing, get another set of patches (one at a time), try 
> again from scratch, etc. etc.

Gotcha.

FWIW, you might try doing the same old process you used to do in SVN -- i.e., 
do it all in a SVN v1.8 checkout like you used to.  And when you're ready to 
commit, just make a patch instead and apply it to a git v1.8 tree.

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

On Oct 2, 2014, at 9:37 AM, Jeff Squyres (jsquyres)  wrote:

> On Oct 2, 2014, at 12:25 PM, Ralph Castain  wrote:
> 
>> No. Getting all the right patches (one at a time) from svn is slow, 
>> and then it doesn't necessarily apply cleanly, so you go back to svn to 
>> figure out what is missing, get another set of patches (one at a time), try 
>> again from scratch, etc. etc.
> 
> Gotcha.
> 
> FWIW, you might try doing the same old process you used to do in SVN -- i.e., 
> do it all in a SVN v1.8 checkout like you used to.  And when you're ready to 
> commit, just make a patch instead and apply it to a git v1.8 tree.

Good suggestion - will do that next time.

> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15981.php

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

On Oct 2, 2014, at 12:37 PM, Ralph Castain  wrote:

> Sonow that I've fought thru and created a pull request, I find that I 
> cannot assign it to anyone for review. The only users on the ompi-release 
> branch are myself and Jeff (plus the ompiteam admin).
> 
> So how do we assign someone to review it?

I think the best way is to do an @mention of someone in the comment.  E.g., in 
this case, "@osvegis, can you review this?"

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Ralph Castain]

On Oct 2, 2014, at 9:43 AM, Jeff Squyres (jsquyres)  wrote:

> On Oct 2, 2014, at 12:37 PM, Ralph Castain  wrote:
> 
>> Sonow that I've fought thru and created a pull request, I find that I 
>> cannot assign it to anyone for review. The only users on the ompi-release 
>> branch are myself and Jeff (plus the ompiteam admin).
>> 
>> So how do we assign someone to review it?
> 
> I think the best way is to do an @mention of someone in the comment.  E.g., 
> in this case, "@osvegis, can you review this?"

How are they going to review it, given they don't have authority to do anything 
on that branch? Can they still comment? Can they reassign them when done?


> 
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15983.php

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Jeff Squyres (jsquyres)]

On Oct 2, 2014, at 12:47 PM, Ralph Castain  wrote:

> How are they going to review it, given they don't have authority to do 
> anything on that branch? Can they still comment? Can they reassign them when 
> done?

Yes, they can comment.

The idea was that they would apply the "reviewed" label when they have reviewed 
it successfully.  These "reviewed" labels will then be easily viewable in the 
PR listing by the RM/GK to know which ones are ready.

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

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Dave Goodell (dgoodell)]

On Oct 2, 2014, at 11:47 AM, Ralph Castain  wrote:

> 
> On Oct 2, 2014, at 9:43 AM, Jeff Squyres (jsquyres)  
> wrote:
> 
>> On Oct 2, 2014, at 12:37 PM, Ralph Castain  wrote:
>> 
>>> Sonow that I've fought thru and created a pull request, I find that I 
>>> cannot assign it to anyone for review. The only users on the ompi-release 
>>> branch are myself and Jeff (plus the ompiteam admin).
>>> 
>>> So how do we assign someone to review it?
>> 
>> I think the best way is to do an @mention of someone in the comment.  E.g., 
>> in this case, "@osvegis, can you review this?"
> 
> How are they going to review it, given they don't have authority to do 
> anything on that branch? Can they still comment? Can they reassign them when 
> done?

They should be able to comment.  I don't think they'll be able to change the 
assignment.

-Dave

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Gilles Gouaillardet]

Ralph,

what about cherry-pick ?

the most painful part is probably to manually retrieve the git commit id
of a given svn commit id

git log master, and then search r
/* each commit log has a line like :
This commit was SVN rx
*/

and once you got (all) the git commits id of a given CMR, you can
cherry-pick them,
and push and issue the PR

/* i did not check whether cherry-pick automatically create/remove files */

Cheers,

Gilles

On 2014/10/03 0:51, Ralph Castain wrote:
> I agree that someone needs to do it. However, what isn't clear is *how* to do 
> it. I get the mechanics:
>
> * clone the ompi-release 1.8 branch
> * apply the required change
> * issue a pull request
>
> It's the second step that isn't clear. How the heck do I (a) find the change 
> that was originally applied, and (b) apply it to my clone of ompi-release???
>
> Do I just download the changeset(s) from Trac and patch them in? I guess that 
> will work if we don't have an alternative method.
>
>
> On Oct 2, 2014, at 3:41 AM, Jeff Squyres (jsquyres)  
> wrote:
>
>> Fair enough.
>>
>> *Someone* needs to re-file those CMRs as pull requests; probably in some 
>> cases it's the reporter, probably in some cases it's the owner.  :-)
>>
>>
>> On Oct 2, 2014, at 6:33 AM, Gilles Gouaillardet 
>>  wrote:
>>
>>> Hi Jeff,
>>>
>>> thumbs up for the migration !
>>>
>>> the names here are the CMR owners ('Owned by' field in TRAC)
>>> should it be the duty of the creators ('Reported by' field in TRAC) to
>>> re-create the CMR instead?
>>>
>>> /* if not, and from a git log point of view, that means the commiter
>>> will be the reviewer and not the reporter */
>>>
>>> what do you think ?
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>> On 2014/10/02 19:24, Jeff Squyres (jsquyres) wrote:
 2. The following still-open CMRs were not brought over, and need to be 
 re-filed as pull requests:

 - https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
 - https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
 - https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
 - https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
 - https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
 - https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
 - https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
 - https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
 - https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
 - https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
 - https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
 - https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
 - https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff
>>> ___
>>> devel mailing list
>>> de...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/devel/2014/10/15966.php
>>
>> -- 
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to: 
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/10/15967.php
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15971.php

Re: [OMPI devel] OMPI@GitHub: (Mostly) Open for business

[Gilles Gouaillardet]

Jeff,

i could not find how to apply a label to a PR via the web interface (and
i am not sure i can even do that since authority might be required)

any idea (maybe a special keyword in the comment ...) ?

Cheers,

Gilles

On 2014/10/03 1:53, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 12:47 PM, Ralph Castain  wrote:
>
>> How are they going to review it, given they don't have authority to do 
>> anything on that branch? Can they still comment? Can they reassign them when 
>> done?
> Yes, they can comment.
>
> The idea was that they would apply the "reviewed" label when they have 
> reviewed it successfully.  These "reviewed" labels will then be easily 
> viewable in the PR listing by the RM/GK to know which ones are ready.
>