[git-help] New libraries?
Today I checked in the new Predef library and I'm wondering, not just for it but in general, if this interim period of svn to git transition what happens to new libraries? Will they automatically show up in the git repos? What are the procedures if the new library is already, originally in git and modularized? Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
on Sun Jul 28 2013, Rene Rivera
Today I checked in the new Predef library and I'm wondering, not just for it but in general, if this interim period of svn to git transition what happens to new libraries? Will they automatically show up in the git repos?
If they are checked in to Boost's SVN and the ruleset is updated appropriately, they'll show up (our modularization build will fail if their paths are not handled in the ruleset).
What are the procedures if the new library is already, originally in git and modularized?
I don't have an answer for that one, sorry. -- Dave Abrahams
On Mon, 29 Jul 2013, at 03:46 AM, Rene Rivera wrote:
What are the procedures if the new library is already, originally in git and modularized?
Odeint is in the same situation, They've just been copying their files into subversion which I imagine is a bit of a pain. I believe the plan is just to switch the git submodule to their repo after conversion, which will hopefully work okay.
on Mon Jul 29 2013, Daniel James
On Mon, 29 Jul 2013, at 03:46 AM, Rene Rivera wrote:
What are the procedures if the new library is already, originally in git and modularized?
Odeint is in the same situation, They've just been copying their files into subversion which I imagine is a bit of a pain. I believe the plan is just to switch the git submodule to their repo after conversion, which will hopefully work okay.
IIUC, we want the submodules in http://github.com/boostorg/boost to keep pointing at repositories under http://github.com/boostorg/. However, it should be easy to push new history to that repository. -- Dave Abrahams
On Fri, 2 Aug 2013, at 06:02 AM, Dave Abrahams wrote:
on Mon Jul 29 2013, Daniel James
wrote: Odeint is in the same situation, They've just been copying their files into subversion which I imagine is a bit of a pain. I believe the plan is just to switch the git submodule to their repo after conversion, which will hopefully work okay.
IIUC, we want the submodules in http://github.com/boostorg/boost to keep pointing at repositories under http://github.com/boostorg/. However, it should be easy to push new history to that repository.
Sure. Maybe odeint and predef should have different names (maybe odeint-svn?), to indicate that they're not the final repo. Or do you want to have the disjoint histories in a single repo?
on Fri Aug 02 2013, Daniel James
On Fri, 2 Aug 2013, at 06:02 AM, Dave Abrahams wrote:
on Mon Jul 29 2013, Daniel James
wrote: Odeint is in the same situation, They've just been copying their files into subversion which I imagine is a bit of a pain. I believe the plan is just to switch the git submodule to their repo after conversion, which will hopefully work okay.
IIUC, we want the submodules in http://github.com/boostorg/boost to keep pointing at repositories under http://github.com/boostorg/. However, it should be easy to push new history to that repository.
Sure. Maybe odeint and predef should have different names (maybe odeint-svn?), to indicate that they're not the final repo. Or do you want to have the disjoint histories in a single repo?
Yes; there's nothing at all wrong with that, and IMO it would be better to have the actual history in there. Given the way the conversion works, they might even turn out not to be totally disjoint. -- Dave Abrahams
participants (3)
-
Daniel James -
Dave Abrahams -
Rene Rivera