Re: [OMPI devel] Open MPI services migration: part 1

2012-06-04 Thread Jeff Squyres
On Jun 1, 2012, at 6:28 PM, George Bosilca wrote: > Here is my guess: he's working on his PhD at Huston under Edgar's > supervision. My point is that if one doesn't know who is behind an svn_id, it > is not by having his email address that the lack of knowledge get resolved. Fair enough -- you

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread George Bosilca
On Jun 2, 2012, at 06:52 , Jeff Squyres wrote: > On Jun 1, 2012, at 5:41 PM, George Bosilca wrote: > >> So basically to achieve the same goal the change moved from a fictitious >> email address to our real one. I agree with you that both the old and the >> new way allows one to know exactly wh

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Jeff Squyres
On Jun 1, 2012, at 5:41 PM, George Bosilca wrote: > So basically to achieve the same goal the change moved from a fictitious > email address to our real one. I agree with you that both the old and the new > way allows one to know exactly who was the committer. But as you highlighted > in your e

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread George Bosilca
So basically to achieve the same goal the change moved from a fictitious email address to our real one. I agree with you that both the old and the new way allows one to know exactly who was the committer. But as you highlighted in your email, the commit messages are intended for a well informed

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Jeff Squyres
On Jun 1, 2012, at 5:17 PM, George Bosilca wrote: > I'm not sure I follow what was "get it right", but Tim's comment is still > valid (look at the from field on the last set of 1.6 commits). Right. Prior to this, commits were from @osl.iu.edu -- which was a fictitious set of email addresses.

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread George Bosilca
I'm not sure I follow what was "get it right", but Tim's comment is still valid (look at the from field on the last set of 1.6 commits). Moreover, these commits contains our real addresses in clear in the text. We all work hard to obfuscate them, I definitively prefer to keep them that way. > A

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Jeff Squyres
Yep -- that was a[n unexpected] feature upgrade when we moved to the new server. :-) (you'll notice that it took a few tries to get it right, too :-) ) On Jun 1, 2012, at 12:52 PM, Tim Mattox wrote: > One minor difference I see from the services migration is that the SVN > commit e-mails on t

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Tim Mattox
One minor difference I see from the services migration is that the SVN commit e-mails on the svn-full mailing list now all appear to be coming from a generic "svn-commit-mai...@open-mpi.org" address, instead of from [commiter's login]@osl.iu.edu. Not a serious bug, but it was useful to scan throug

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Jeff Squyres
The migration is now complete. Let us know if you run into any problems. On Jun 1, 2012, at 6:53 AM, Jeff Squyres wrote: > Don't forget -- these services will be offline while they are migrated > starting in about 2 hours. > > On May 30, 2012, at 2:44 PM, Jeff Squyres wrote: > >> Be advised

Re: [OMPI devel] Open MPI services migration: part 1

2012-06-01 Thread Jeff Squyres
Don't forget -- these services will be offline while they are migrated starting in about 2 hours. On May 30, 2012, at 2:44 PM, Jeff Squyres wrote: > Be advised that I have received the following message from our Indiana U. > hosting provider. SVN/Trac/OpenGrok will be unavailable during the ti

[OMPI devel] Open MPI services migration: part 1

2012-05-30 Thread Jeff Squyres
Be advised that I have received the following message from our Indiana U. hosting provider. SVN/Trac/OpenGrok will be unavailable during the time frame described below. More migrations will follow (e.g., web services) in the coming weeks; stay tuned. - We are planning to move all the serv