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?
>

Re: [hwloc-devel] Move to git?

[David Beer]

I know I'm not really an active member of the dev community, but I have
experience with this from working on TORQUE (my full-time job). We switched
to git (hosted on github) and it has been fantastic for us. I was familiar
with git but hardly an expert when we changed over, and the same was true
of a lot of our community. Largely having to learn another tool has been a
non-event and github has had a lot of useful features that have helped us
coordinate with our community better.

I wasn't responsible for switching things, but I believe we used svn2git
and it did change all of the r to git changesets.

David


On Tue, Jun 4, 2013 at 8:05 AM, Nathan Hjelm  wrote:

> Take a look at svn2git. It takes care of some the the tag/branch naming
> problems. If you use it make sure to pass the --metadata option to get the
> git-svn-id's in the commit messages.
>
> -Nathan
>
> On Jun 4, 2013, at 4:23 AM, Brice Goglin  wrote:
>
> > When I switched Open-MX and KNEM from SVN to GIT, I basically just
> > pushed my git-svn clone. But I had to manually convert some svn
> > tags/branches. IIRC, the main reason is that git-svn has a strange way
> > to name svn branches in git.
> >
> > We may also have to pass --authors-file to git svn clone so that SVN
> > logins are converted into proper git author names.
> >
> > 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?
> >>
> >
> > ___
> > hwloc-devel mailing list
> > hwloc-de...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
>
>
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
>



-- 
David Beer | Senior Software Engineer
Adaptive Computing

Re: [hwloc-devel] Move to git?

[Nathan Hjelm]

Take a look at svn2git. It takes care of some the the tag/branch naming 
problems. If you use it make sure to pass the --metadata option to get the 
git-svn-id's in the commit messages.

-Nathan

On Jun 4, 2013, at 4:23 AM, Brice Goglin  wrote:

> When I switched Open-MX and KNEM from SVN to GIT, I basically just
> pushed my git-svn clone. But I had to manually convert some svn
> tags/branches. IIRC, the main reason is that git-svn has a strange way
> to name svn branches in git.
> 
> We may also have to pass --authors-file to git svn clone so that SVN
> logins are converted into proper git author names.
> 
> 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?
>> 
> 
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel

Re: [hwloc-devel] Move to git?

[Jeff Squyres (jsquyres)]

On Jun 4, 2013, at 3:38 AM, Brice Goglin  wrote:

>> I'd like to explore converting all the old SVN log message mentions of 
>> "r" to git hashes.  git-svn doesn't do that, right?
> 
> No it doesn't afaik, and that would be nice.


I know that MPICH went through this (converting all old messages -- both in SVN 
and trac -- from "r" to git hashes).  Let me talk to Dave later today and 
see what they did.

-- 
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?

[Jeff Squyres (jsquyres)]

On Jun 4, 2013, at 3:23 AM, Brice Goglin  wrote:

> When I switched Open-MX and KNEM from SVN to GIT, I basically just
> pushed my git-svn clone. But I had to manually convert some svn
> tags/branches. IIRC, the main reason is that git-svn has a strange way
> to name svn branches in git.

I'd like to explore converting all the old SVN log message mentions of "r" 
to git hashes.  git-svn doesn't do that, right?

> We may also have to pass --authors-file to git svn clone so that SVN
> logins are converted into proper git author names.

K.

-- 
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]

When I switched Open-MX and KNEM from SVN to GIT, I basically just
pushed my git-svn clone. But I had to manually convert some svn
tags/branches. IIRC, the main reason is that git-svn has a strange way
to name svn branches in git.

We may also have to pass --authors-file to git svn clone so that SVN
logins are converted into proper git author names.

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?
>

Re: [hwloc-devel] Move to git?

[Jeff Squyres (jsquyres)]

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]

+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/
>
>
>___
>hwloc-devel mailing list
>hwloc-de...@open-mpi.org
>http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel

[hwloc-devel] Move to git?

[Jeff Squyres (jsquyres)]

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/