Re: [hwloc-devel] Move to git?

[Jeff Squyres (jsquyres)]

Go ahead and push now.

I started my git discussions with Dave, but haven't finished them yet.  I don't 
think DongInn has done his part at IU yet.  I think this will take a short 
while to get done; it won't happen immediately.


On Jun 12, 2013, at 1:52 PM, Brice Goglin  wrote:

> Do you have any svn/git plan in the very near future? I will have a
> couple fixes to push in the next days. So if you're going to switch to
> git soon, please let me know, I'll wait and commit later.
> 
> Brice
> 
> 
> 
> Le 04/06/2013 12:14, Jeff Squyres (jsquyres) a écrit :
>> Ok.  This is kinda what I assumed your response would be.  :-)
>> 
>> Let me talk to Dave Goodell later today, who just recently went through 
>> converting MPICH from SVN -> Git, and see what kinds of things we need to do 
>> to get the ball rolling here, and what kinds of dragons we should expect to 
>> encounter along the way.
>> 
>> 
>> On Jun 3, 2013, at 11:17 PM, Brice Goglin  wrote:
>> 
>>> +1000 !
>>> I already use git-svn for most of my hwloc work. But I still need svn for 
>>> backports, and that wastes a lot of my time.
>>> Brice
>>> 
>>> 
>>> "Jeff Squyres (jsquyres)"  a écrit :
>>> We're having a discussion (again :-) ) about moving OMPI to a DVCS.
>>> 
>>> The short conclusion of the long conversation is: the OMPI dev community 
>>> would be much more comfortable moving to a DVCS if they could see some 
>>> success with other OMPI projects (e.g., hwloc and/or MTT).
>>> 
>>> Would hwloc be interested in moving to git?  This would mean:
>>> 
>>> 1. converting the existing svn to git
>>> --> including all historical log messages that refer to "r"
>>> 2. converting the existing trac to git
>>> --> including all trac tickets, comments, and wiki pages that refer to 
>>> "r"
>>> 
>>> The OMPI devs -- who are mostly unfamiliar with git -- would like to see 
>>> some close-to-home successes with git over a period of time that don't 
>>> require heavy administrative maintenance over time (one of the pushback 
>>> issues was that some organizations have hired full-time people to
>>> maintain/fix git repositories when they break/become unusable).
>>> 
>>> 
>>> Interested?
>> 
> 


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

Re: [hwloc-devel] Move to git?

[Brice Goglin]

Do you have any svn/git plan in the very near future? I will have a
couple fixes to push in the next days. So if you're going to switch to
git soon, please let me know, I'll wait and commit later.

Brice



Le 04/06/2013 12:14, Jeff Squyres (jsquyres) a écrit :
> Ok.  This is kinda what I assumed your response would be.  :-)
>
> Let me talk to Dave Goodell later today, who just recently went through 
> converting MPICH from SVN -> Git, and see what kinds of things we need to do 
> to get the ball rolling here, and what kinds of dragons we should expect to 
> encounter along the way.
>
>
> On Jun 3, 2013, at 11:17 PM, Brice Goglin  wrote:
>
>> +1000 !
>> I already use git-svn for most of my hwloc work. But I still need svn for 
>> backports, and that wastes a lot of my time.
>> Brice
>>
>>
>> "Jeff Squyres (jsquyres)"  a écrit :
>> We're having a discussion (again :-) ) about moving OMPI to a DVCS.
>>
>> The short conclusion of the long conversation is: the OMPI dev community 
>> would be much more comfortable moving to a DVCS if they could see some 
>> success with other OMPI projects (e.g., hwloc and/or MTT).
>>
>> Would hwloc be interested in moving to git?  This would mean:
>>
>> 1. converting the existing svn to git
>> --> including all historical log messages that refer to "r"
>> 2. converting the existing trac to git
>> --> including all trac tickets, comments, and wiki pages that refer to 
>> "r"
>>
>> The OMPI devs -- who are mostly unfamiliar with git -- would like to see 
>> some close-to-home successes with git over a period of time that don't 
>> require heavy administrative maintenance over time (one of the pushback 
>> issues was that some organizations have hired full-time people to
>> maintain/fix git repositories when they break/become unusable).
>>
>>
>> Interested?
>